https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88421
Andrew Pinski changed:
What|Removed |Added
Host||shle--netbsdelf
Build|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88421
--- Comment #6 from Jonathan Wakely ---
(In reply to coypu from comment #1)
> suggested change: put #include_next outside of include guards?
We did something similar for PR 69581
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88421
--- Comment #5 from coypu ---
(In reply to Jakub Jelinek from comment #4)
> That is one header, not two, so why should that fenv.h's #include_next
> include that same header or some copy of that header in a different path?
I am in the process
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88421
--- Comment #4 from Jakub Jelinek ---
That is one header, not two, so why should that fenv.h's #include_next include
that same header or some copy of that header in a different path?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88421
--- Comment #3 from coypu ---
include/c_compatibility/fenv.h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88421
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88421
--- Comment #1 from coypu ---
suggested change: put #include_next outside of include guards?
