https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93421
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|NEW
Assignee|redi at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93421
--- Comment #11 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:b108faa9400e13a3d00dd7f71cff0ac45e29c5c9
commit r11-5167-gb108faa9400e13a3d00dd7f71cff0ac45e29c5c9
Author: Jonathan Wakely
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93421
--- Comment #10 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:1e3e6c700f04fe6992b9077541e434172c1cbdae
commit r11-5114-g1e3e6c700f04fe6992b9077541e434172c1cbdae
Author: Jonathan Wakely
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93421
--- Comment #9 from Jonathan Wakely ---
(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 an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93421
--- Comment #8 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:4d039cb9a1d0ffc6910fe09b726c3561b64527dc
commit r11-5022-g4d039cb9a1d0ffc6910fe09b726c3561b64527dc
Author: Jonathan Wakely
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93421
--- Comment #7 from Rich Felker ---
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93421
--- Comment #6 from Jonathan Wakely ---
On second thoughts, we probably don't need to worry about
SYS_clock_gettime_time64. We only use SYS_clock_gettime syscalls on old glibc
systems where clock_gettime is in librt not libc, and those systems ar
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93421
Jonathan Wakely changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93421
--- Comment #4 from Rich Felker ---
Actually I didn't see it, I just saw Florian added to CC and it reminded me of
the issue, which reminded me I needed to check this for riscv32 issues with the
riscv32 port pending merge. :-)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93421
--- Comment #3 from Jonathan Wakely ---
Ack. I assume you saw PR 97182 and that's what prompted your comment. Otherwise
it's quite a coincidence :)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93421
--- Comment #2 from Rich Felker ---
Rather than #if defined(SYS_futex_time64), I think it should be made:
#if defined(SYS_futex_time64) && SYS_futex_time64 != SYS_futex
This is in consideration of support for riscv32 and future archs without le
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93421
--- Comment #1 from Jonathan Wakely ---
(In reply to Rich Felker from comment #0)
> Created attachment 47704 [details]
> simple fix, not necessarily right for upstream
I like this solution for upstream too. It's simple and it works.
> This assu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93421
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
13 matches
Mail list logo
