[Bug c++/81513] __has_cpp_attribute returns non-zero in C++03 mode, but attributes don't work

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81513 Pavel Roskin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c++/81513] __has_cpp_attribute returns non-zero in C++03 mode, but attributes don't work

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81513 --- Comment #4 from Andreas Schwab --- > #if __cpp_attributes >= 200809 && defined(__has_cpp_attribute) \ > && __has_cpp_attribute(maybe_unused) This will result in a syntax error if the compiler does not support

[Bug c++/81513] __has_cpp_attribute returns non-zero in C++03 mode, but attributes don't work

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81513 Jonathan Wakely changed: What|Removed |Added CC||jason at gcc dot gnu.org --- Comment

[Bug c++/81513] __has_cpp_attribute returns non-zero in C++03 mode, but attributes don't work

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81513 --- Comment #2 from Pavel Roskin --- __has_cpp_attribute is not supposed to check if the functionality is available somehow using some other approaches and keywords. It is supposed to check if the functionality is available as an attribute.

[Bug c++/81513] __has_cpp_attribute returns non-zero in C++03 mode, but attributes don't work

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81513 --- Comment #1 from Jonathan Wakely --- The C++11 attribute syntax isn't supported in C++03 mode, but the noreturn attribute is supported using the GNU attribute syntax (and has been for years) so it's right for that to be non-zero. I'm not sure