Adhemerval Zanella a4ed0471d7 Always define __USE_TIME_BITS64 when 64 bit time_t is used ... It was raised on libc-help [1] that some Linux kernel interfaces expect the libc to define __USE_TIME_BITS64 to indicate the time_t size for the kABI. Different than defined by the initial y2038 design document [2], the __USE_TIME_BITS64 is only defined for ABIs that support more than one time_t size (by defining the _TIME_BITS for each module). The 64 bit time_t redirects are now enabled using a different internal define (__USE_TIME64_REDIRECTS). There is no expected change in semantic or code generation. Checked on x86_64-linux-gnu, i686-linux-gnu, aarch64-linux-gnu, and arm-linux-gnueabi [1] https://sourceware.org/pipermail/libc-help/2024-January/006557.html [2] https://sourceware.org/glibc/wiki/Y2038ProofnessDesign Reviewed-by: DJ Delorie <dj@redhat.com>		2024-04-02 15:28:36 -03:00
..
sys
ftok.c
Makefile
msgctl.c
msgget.c
msgrcv.c
msgsnd.c
semctl.c
semget.c
semop.c
semtimedop.c
shmat.c
shmctl.c
shmdt.c
shmget.c
test-sysvipc.h
test-sysvmsg-time64.c
test-sysvmsg.c
test-sysvsem-time64.c
test-sysvsem.c
test-sysvshm-time64.c
test-sysvshm.c
Versions