summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorRich Felker <dalias@aerifal.cx>2019-12-17 18:19:05 -0500
committerRich Felker <dalias@aerifal.cx>2019-12-17 18:19:05 -0500
commitf12bd8e05c8bb2c3e2b91d635887ec424ef8fbd9 (patch)
tree3422273fde4f27abb33b8e4554737475b7581463 /README
parent9432bbd4e880850357fd0a81b429499451eb2084 (diff)
downloadmusl-f12bd8e05c8bb2c3e2b91d635887ec424ef8fbd9.tar.gz
musl-f12bd8e05c8bb2c3e2b91d635887ec424ef8fbd9.tar.bz2
musl-f12bd8e05c8bb2c3e2b91d635887ec424ef8fbd9.tar.xz
musl-f12bd8e05c8bb2c3e2b91d635887ec424ef8fbd9.zip
signal to kernel headers that time_t is 64-bit
linux/input.h and perhaps others use this macro to determine whether the userspace time_t is 64-bit when potentially defining types in terms of time_t and derived structures. the name __USE_TIME_BITS64 is unfortunate; it really should have been in the __UAPI namespace. but this is what was chosen back in v4.16 when first preparing input.h for time64 userspace, presumably based on expectations about what the glibc-internal features.h macro for time64 would be, and changing it now would just put a new minimum version requirement on kernel headers. the __USE_TIME_BITS64 macro is not intended as a public interface. it is purely an internal contract between libc and Linux uapi headers.
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions