On 2/4/20 3:52 AM, Jakub Jelinek wrote:
Hi!
The standard says http://eel.is/c++draft/cpp.cond#7.sentence-2 that
__has_include can't appear at arbitrary places in the source. As we have
not recognized __has_include* outside of preprocessing directives in the
past, accepting it there now would be a regression. The patch does still
allow it in #define if it is then used in preprocessing directives, I guess
that use isn't strictly valid either, but clang seems to accept it.
Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
yes, thanks!
--
Nathan Sidwell