[Bug preprocessor/110558] __has_include argument expansion results in unexpected filename

2024-03-14 Thread lhyatt at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110558 Lewis Hyatt changed: What|Removed |Added Target Milestone|--- |14.0 Resolution|---

[Bug preprocessor/110558] __has_include argument expansion results in unexpected filename

2024-03-14 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110558 --- Comment #6 from GCC Commits --- The master branch has been updated by Lewis Hyatt : https://gcc.gnu.org/g:942497ad74272e0ef16020d628e471c5f21474b0 commit r14-9465-g942497ad74272e0ef16020d628e471c5f21474b0 Author: Lewis Hyatt Date: Tue

[Bug preprocessor/110558] __has_include argument expansion results in unexpected filename

2023-12-12 Thread lhyatt at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110558 Lewis Hyatt changed: What|Removed |Added Keywords||patch URL|

[Bug preprocessor/110558] __has_include argument expansion results in unexpected filename

2023-12-11 Thread lhyatt at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110558 Lewis Hyatt changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0

[Bug preprocessor/110558] __has_include argument expansion results in unexpected filename

2023-12-11 Thread fw at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110558 --- Comment #3 from Florian Weimer --- It tries to read "my. header.h" for some reason, even though the MAKE_INCLUDE_PATH macro produces "my.header.h" in other contexts (not just in #include directives). I doubt this is related to bug 80753.

[Bug preprocessor/110558] __has_include argument expansion results in unexpected filename

2023-07-05 Thread provisorisch at online dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110558 --- Comment #2 from provisorisch at online dot de --- Not quite, but you will run into bug 80753 if the header file does not exist: The second #include will not cause an error in that case. The first #include however will cause an error as

[Bug preprocessor/110558] __has_include argument expansion results in unexpected filename

2023-07-05 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110558 Andrew Pinski changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill