[Bug libstdc++/79433] __has_include does not conform to SD-6

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79433

Jonathan Wakely  changed:

   What|Removed |Added

   Severity|normal  |enhancement

--- Comment #12 from Jonathan Wakely  ---
(In reply to Marc Mutz from comment #9)
> __has_include these days is defined by SD-6,

Nope, it's defined normatively in the C++17 draft not SD-6, and it says a
"has-include-expression evaluates to 1 if the search for the source file
succeeds, and to 0 if the search fails." That is very clear, and we do exactly
that. The intended use case in SD-6 is not relevant, the C++ draft standard is
clear, and we conform to it.

[Bug libstdc++/79433] __has_include does not conform to SD-6

[marc.mutz at kdab dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79433

--- Comment #11 from Marc Mutz  ---
Fair enough. Sorry for filing it under the wrong component.

[Bug libstdc++/79433] __has_include does not conform to SD-6

[pinskia at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79433

Andrew Pinski  changed:

   What|Removed |Added

  Component|c++ |libstdc++

--- Comment #10 from Andrew Pinski  ---
(In reply to Marc Mutz from comment #9)
> __has_include these days is defined by SD-6, and while not spelled out in
> normative text, the intent is very much for it to be able to detect presence
> of a header for inclusion.

Then the bug is in the header (library) and not in the preprocessor or the
front-end.