This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug preprocessor/63662] __has_include is not implemented but it is defined, so "#ifdef __has_include" guards are ineffective in blocking usage of __has_include
- From: "andre.mccurdy at linaro dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 28 Oct 2014 02:25:43 +0000
- Subject: [Bug preprocessor/63662] __has_include is not implemented but it is defined, so "#ifdef __has_include" guards are ineffective in blocking usage of __has_include
- Auto-submitted: auto-generated
- References: <bug-63662-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63662
andre.mccurdy at linaro dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|__has_include defined but |__has_include is not
|not implemented |implemented but it is
| |defined, so "#ifdef
| |__has_include" guards are
| |ineffective in blocking
| |usage of __has_include
--- Comment #3 from andre.mccurdy at linaro dot org ---
Thanks. I have updated the original summary since it was unclear:
The bug is not that the __has_include feature can't be used in 4.9.x.
The bug is that __has_include is defined in gcc-4_9-branch, which causes
"#ifdef __has_include" be ineffective as a guard to prevent attempts to use the
__has_include feature.