diff options
| author | Alistair Francis <alistair.francis@wdc.com> | 2019-12-23 11:45:01 -0800 |
|---|---|---|
| committer | Alistair Francis <alistair.francis@wdc.com> | 2020-04-02 09:21:06 -0700 |
| commit | a51e03588937ad804a9f583ea3d0fc0a4d088c33 (patch) | |
| tree | f77bf16cbc4562ca3cc40625042406f20f230e78 /bits/time.h | |
| parent | 1c634e677f584ea264f984eb408a5142150af855 (diff) | |
| download | glibc-a51e03588937ad804a9f583ea3d0fc0a4d088c33.zip glibc-a51e03588937ad804a9f583ea3d0fc0a4d088c33.tar.gz glibc-a51e03588937ad804a9f583ea3d0fc0a4d088c33.tar.bz2 | |
linux: Use long time_t __getitimer/__setitimer
The Linux kernel expects itimerval to use a 32-bit time_t, even on archs
with a 64-bit time_t (like RV32). To address this let's convert
itimerval to/from 32-bit and 64-bit to ensure the kernel always gets
a 32-bit time_t.
While we are converting these functions let's also convert them to be
the y2038 safe versions. This means there is a *64 function that is
called by a backwards compatible wrapper.
Tested-by: Lukasz Majewski <lukma@denx.de>
Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Diffstat (limited to 'bits/time.h')
0 files changed, 0 insertions, 0 deletions