https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65377
Markus Trippelsdorf trippels at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65377
npl at chello dot at changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65377
Markus Trippelsdorf trippels at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65377
--- Comment #7 from Markus Trippelsdorf trippels at gcc dot gnu.org ---
Unfortunately https://gcc.gnu.org/ml/gcc-patches/2015-01/msg02357.html hasn't
been checked in yet.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65377
--- Comment #6 from npl at chello dot at ---
(In reply to npl from comment #3)
1) It simply shouldnt fail.
2) this is a generic header for C and C++.
__has_cpp_attribute(clang::fallthrough) should resolve to 0 and not fail.
This is a bug in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65377
--- Comment #8 from npl at chello dot at ---
This (and the Iso recommendation) doesnt answer the question whether the
__has_cpp_attribute macro should be defined for C sources either (it seems
illogical to me).
Guess its undefined and not a bug,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65377
Marek Polacek mpolacek at gcc dot gnu.org changed:
What|Removed |Added
CC||mpolacek at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65377
--- Comment #5 from Andrew Pinski pinskia at gcc dot gnu.org ---
Use the proper check if you are want check if you are compiling c++ code first.
