https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93421
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
Status|NEW |ASSIGNED
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Created attachment 49267
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49267&action=edit
Proposed fix
Rich, does this work for musl?
As glibc hasn't updated its userspace timespec yet I have no way to test
whether this fixes the problem, because I don't have the problem.
Is inspecting __USE_TIME_BITS64 allowed with musl? The current proposal at
https://sourceware.org/glibc/wiki/Y2038ProofnessDesign#API_design says users
can check if that's defined, although usually the __USE_xxx macros are not
meant for public consumption.
