https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93421
--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Rich Felker from comment #7) > Indeed, the direct clock_gettime syscall stuff is just unnecessary on any > modern system, certainly any time64 one. I read the patch briefly and I > don't see anywhere it would break anything, but it also wouldn't produce a > useful Y2038-ready configuration, so I don't think it makes sense. Configure > or source-level assertions should just ensure that, if time_t is larger than > long and there's a distinct time64 syscall, the direct syscall is never used. I didn't get around to making use of the new syscalls for GCC 11, so I've committed that patch. I'll keep this bug open to revisit it and do it properly later.
