Adhemerval Zanella dd535f4f19 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> (cherry picked from commit a4ed0471d7)		2024-05-28 07:30:07 +02:00
..
bits
sys	Always define __USE_TIME_BITS64 when 64 bit time_t is used	2024-05-28 07:30:07 +02:00
accept4.c
accept.c
bind.c
connect.c
getpeername.c
getsockname.c
getsockopt.c
isfdtype.c
listen.c
Makefile
opensock.c
recv.c
recvfrom.c
recvmmsg.c
recvmsg.c
sa_len.c
send.c
sendmmsg.c
sendmsg.c
sendto.c
setsockopt.c
shutdown.c
sockaddr_un_set.c
sockatmark.c
socket.c
socketpair.c
tst-accept4.c
tst-cmsg_cloexec.c
tst-cmsghdr-skeleton.c
tst-cmsghdr.c
tst-connect.c
tst-sockaddr_un_set.c
tst-sockopt-time64.c
tst-sockopt.c
Versions