diff options
author | Alistair Francis <alistair.francis@wdc.com> | 2019-06-21 11:31:56 -0700 |
---|---|---|
committer | Alistair Francis <alistair.francis@wdc.com> | 2020-08-27 08:17:41 -0700 |
commit | 2b09ebeee766be3678896b2a0e61e54a8ad10128 (patch) | |
tree | 025bc2c531ef5c05f7bfa2a179213677ecf5ad4d /rt | |
parent | fda4d81801e9d972c029fb4ed1162b960eb540b5 (diff) | |
download | glibc-2b09ebeee766be3678896b2a0e61e54a8ad10128.tar.gz glibc-2b09ebeee766be3678896b2a0e61e54a8ad10128.tar.xz glibc-2b09ebeee766be3678896b2a0e61e54a8ad10128.zip |
RISC-V: Use 64-bit time_t and off_t for RV32 and RV64
Using the original glibc headers under bits/ let's make small modifications to use 64-bit time_t and off_t for both RV32 and RV64. For the typesizes.h, here are justifications for the changes from the generic version (based on Arnd's very helpful feedback): - All the !__USE_FILE_OFFSET64 types (__off_t, __ino_t, __rlim_t, ...) are changed to match the 64-bit replacements. - __time_t is defined to 64 bit, but no __time64_t is added. This makes sense as we don't have the time64 support for other 32-bit architectures yet, and it will be easy to change when that happens. - __suseconds_t is 64-bit. This matches what we use the kernel ABI for the few drivers that are relying on 'struct timeval' input arguments in ioctl, as well as the adjtimex system call. It means that timeval has to be defined without the padding, unlike timespec, which needs padding. Reviewed-by: Maciej W. Rozycki <macro@wdc.com>
Diffstat (limited to 'rt')
0 files changed, 0 insertions, 0 deletions