diff options
author | Lukasz Majewski <lukma@denx.de> | 2020-09-18 20:54:13 +0200 |
---|---|---|
committer | Lukasz Majewski <lukma@denx.de> | 2020-10-15 09:35:43 +0200 |
commit | 29e9874a048f47e2d46c40253036c8d2de921548 (patch) | |
tree | 89bf596e3db06ad009bca5ba0b5ee947732d8f68 /include | |
parent | 9ebaabeaac1a96b0d91f52902ce1dbf4f5a562dd (diff) | |
download | glibc-29e9874a048f47e2d46c40253036c8d2de921548.tar.gz glibc-29e9874a048f47e2d46c40253036c8d2de921548.tar.xz glibc-29e9874a048f47e2d46c40253036c8d2de921548.zip |
y2038: nptl: Convert pthread_mutex_{clock|timed}lock to support 64 bit
The pthread_mutex_clocklock and pthread_mutex_timedlock have been converted to support 64 bit time. This change uses: - New __futex_clocklock_wait64 (instead of lll_timedwait) from ./sysdeps/nptl/futex-helpers.c and - New __futex_clocklock64 function (instead of lll_clocklock) - New futex_lock_pi64 defined in sysdeps/nptl/futex-internal.h The pthread_mutex_{clock|timed}lock only accepts absolute time. Moreover, there is no need to check for NULL passed as *abstime pointer to the syscalls as those calls have exported symbols marked with __nonull attribute for abstime. Some architectures - namely x86, powerpc and s390 - do support lock elision. For those - adjustments have been made in arch specific elision-*.c files to use __futex_clocklock64 instead of lll_clocklock. The __lll_lock_elision (aliased to __lll_clocklock_elision in e.g. sysdeps/unix/sysv/linux/s390/elision-timed.c) just uses, in this patch provided, __futex_clocklock64. For systems with __TIMESIZE != 64 && __WORDSIZE == 32: - Conversions between 64 bit time to 32 bit are necessary - Redirection to pthread_mutex_{clock|timed}lock will provide support for 64 bit time Build tests: ./src/scripts/build-many-glibcs.py glibcs Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions