diff options
| author | Adhemerval Zanella <adhemerval.zanella@linaro.org> | 2024-01-18 10:18:01 -0300 |
|---|---|---|
| committer | Florian Weimer <fweimer@redhat.com> | 2024-05-28 07:30:07 +0200 |
| commit | dd535f4f19ef2b5c367a362af445ecadcf45401e (patch) | |
| tree | 9a5ed482f0baeb50c09ce587836918cb74fe5acb /benchtests | |
| parent | 26e7005728f0eea2972474e6be2905c467661237 (diff) | |
| download | glibc-dd535f4f19ef2b5c367a362af445ecadcf45401e.zip glibc-dd535f4f19ef2b5c367a362af445ecadcf45401e.tar.gz glibc-dd535f4f19ef2b5c367a362af445ecadcf45401e.tar.bz2 | |
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 a4ed0471d71739928a0d0fa3258b3ff3b158e9b9)
Diffstat (limited to 'benchtests')
0 files changed, 0 insertions, 0 deletions