summaryrefslogtreecommitdiff
path: root/arch/or1k
diff options
context:
space:
mode:
authorRich Felker <dalias@aerifal.cx>2019-07-29 21:03:01 -0400
committerRich Felker <dalias@aerifal.cx>2019-07-29 21:03:01 -0400
commit6a4a1691a0653bd51a30c2b8ac19448b7ebac796 (patch)
tree1a004286f76c583abafa03b2b2f9623a3f4639d1 /arch/or1k
parent558c01338b0b635632e70af6ec8a484ca70b0328 (diff)
downloadmusl-6a4a1691a0653bd51a30c2b8ac19448b7ebac796.tar.gz
musl-6a4a1691a0653bd51a30c2b8ac19448b7ebac796.tar.bz2
musl-6a4a1691a0653bd51a30c2b8ac19448b7ebac796.tar.xz
musl-6a4a1691a0653bd51a30c2b8ac19448b7ebac796.zip
recvmmsg: add time64 syscall support, decouple 32-bit time_t
the time64 syscall is used only if the timeout does not fit in 32 bits. after preprocessing, the code is unchanged on 64-bit archs. for 32-bit archs, the timeout now goes through an intermediate copy, meaning that the caller does not get back the updated timeout. this is based on my reading of the documentation, which does not document the updating as a contract you can rely on, and mentions that the whole recvmmsg timeout mechanism is buggy and unlikely to be useful. if it turns out that there's interest in making the remaining time officially available to callers, such functionality could be added back later.
Diffstat (limited to 'arch/or1k')
0 files changed, 0 insertions, 0 deletions