https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96952
--- Comment #9 from Jonathan Wakely ---
No, I didn't say none of them come from configure. What I meant by "checking
anything at configure time" is anything related to the properties of the
compiler that ends up including the header. Not *anythin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96952
--- Comment #8 from Eric Botcazou ---
> Sorry, but it doesn't work. How do you suggest libstdc++ should use
> configure-time checks to find out what features are present in the compiler
> including the libstdc++ headers later? I don't know what t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96952
--- Comment #7 from Jonathan Wakely ---
(In reply to Eric Botcazou from comment #4)
> What about detecting the support at configure time and defining a macro
> during the compilation? Everyone has been doing this for more that 3
> decades...
So
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96952
--- Comment #6 from Eric Botcazou ---
> The whole point of __has_builtin is to let you avoid the configure-time
> checks on compilers that support __has_builtin. If __has_builtin doesn't
> actually work, it's pointless that it even exists and ind
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96952
--- Comment #5 from Rich Felker ---
The whole point of __has_builtin is to let you avoid the configure-time checks
on compilers that support __has_builtin. If __has_builtin doesn't actually
work, it's pointless that it even exists and indeed ever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96952
Eric Botcazou changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96952
Rich Felker changed:
What|Removed |Added
CC||bugdal at aerifal dot cx
--- Comment #3 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96952
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96952
Florian Weimer changed:
What|Removed |Added
CC||fw at gcc dot gnu.org
See Als
