[Bug c/108796] GCC 13 accepts [[noreturn]] attribute without -std=c2x

2023-02-14 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108796

Andrew Pinski  changed:

   What|Removed |Added

 Resolution|DUPLICATE   |---
 Status|RESOLVED|UNCONFIRMED

--- Comment #4 from Andrew Pinski  ---
Actually in this case it is slightly different.
Let me reopen it for a second.

[Bug c/108796] GCC 13 accepts [[noreturn]] attribute without -std=c2x

2023-02-14 Thread sam at gentoo dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108796

Sam James  changed:

   What|Removed |Added

 Resolution|INVALID |DUPLICATE

--- Comment #3 from Sam James  ---


*** This bug has been marked as a duplicate of bug 101682 ***

[Bug c/108796] GCC 13 accepts [[noreturn]] attribute without -std=c2x

2023-02-14 Thread sam at gentoo dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108796

--- Comment #2 from Sam James  ---
Sorry, for completeness, I meant to include:
```
$ gcc-12 -O2 /tmp/foo.c # ditto with -std=c89
/tmp/foo.c:3:1: warning: 'noreturn' attribute ignored [-Wattributes]
3 | [[noreturn]] void foo(void) {
  | ^
``

[Bug c/108796] GCC 13 accepts [[noreturn]] attribute without -std=c2x

2023-02-14 Thread sam at gentoo dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108796

Sam James  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Sam James  ---
I asked on #gcc and this is intentional, it seems.