https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97182
Bug ID: 97182
Summary: Add support for targets that only define
SYS_futex_time64 and not SYS_futex
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: redi at gcc dot gnu.org
Target Milestone: ---
I'm told this affects 32-bit RISC-V.
If SYS_futex isn't defined then libstdc++ won't use futexes, even though they
might be available via the new SYS_futex_time64 syscall instead.
The autoconf checks for SYS_futex should be updated to look for
SYS_futex_time64 as well, and then src/c++11/futex.cc needs to use the best one
available, and possibly have a fallback for the case where both were defined at
configure time but one returns ENOSYS at runtime. Ugh.
This probably also affects our uses of SYS_clock_gettime in both
src/c++11/futex.cc and src/c++11/chrono.cc
