https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80753
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80753
--- Comment #7 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:37f373e974ac0a272b0e2b24e27c08833ad43470
commit r14-1870-g37f373e974ac0a272b0e2b24e27c08833ad43470
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80753
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80753
Andrew Pinski changed:
What|Removed |Added
CC||jpegqs at gmail dot com
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80753
--- Comment #4 from Matthijs Kooijman ---
I looked a bit at the source, and it seems the the problem is (not
surprisingly) that `__has_include` causes the header filename to be put into
the cache, and an error message is only generated when the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80753
Matthijs Kooijman changed:
What|Removed |Added
CC||matthijs at stdin dot nl
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80753
--- Comment #2 from Jonathan Wakely ---
This means the following paradox compiles OK:
#if ! __has_include()
# include
#endif
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80753
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80753
--- Comment #1 from Pekka S ---
Created attachment 41357
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41357=edit
__has_include_next testcase on a non-existent file