diff options
author | Rich Felker <dalias@aerifal.cx> | 2019-10-19 21:29:55 -0400 |
---|---|---|
committer | Rich Felker <dalias@aerifal.cx> | 2019-10-19 21:29:55 -0400 |
commit | 5850546e9669f793aab61dfc7c4f2c1ff35c4b29 (patch) | |
tree | 6edcd74d9a2b449fd013692cc5cbf25ae78538b8 /include | |
parent | 7e8171143124f7f510db555dc6f6327a965a3e84 (diff) | |
download | musl-5850546e9669f793aab61dfc7c4f2c1ff35c4b29.tar.gz musl-5850546e9669f793aab61dfc7c4f2c1ff35c4b29.tar.bz2 musl-5850546e9669f793aab61dfc7c4f2c1ff35c4b29.tar.xz musl-5850546e9669f793aab61dfc7c4f2c1ff35c4b29.zip |
wait4, getrusage: add time64/x32 variant
presently the kernel does not actually define time64 versions of these
syscalls, and they're not really needed except to represent extreme
cpu time usage. however, x32's versions of the syscalls already behave
as time64 ones, meaning the functions were broken on x32 if the caller
used any part of the rusage result other than ru_utime and ru_stime.
commit 7e8171143124f7f510db555dc6f6327a965a3e84 made it possible to
fix this by treating x32's syscalls as time64 versions.
in the non-time64-syscall case, make the syscall with the rusage
destination pointer adjusted so that all members but the timevals line
up between the libc and kernel structures. on 64-bit archs, or present
32-bit archs with 32-bit time_t, the timevals will line up too and no
further work is needed. for future 32-bit archs with 64-bit time_t,
the timevals are copied into place, contingent on time_t being larger
than long.
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions