public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/108213] New: [[noreturn]] cannot be used after static keyword
@ 2022-12-23 15:41 marxin at gcc dot gnu.org
  2022-12-23 15:46 ` [Bug c/108213] " pinskia at gcc dot gnu.org
  2022-12-27 10:14 ` marxin at gcc dot gnu.org
  0 siblings, 2 replies; 3+ messages in thread
From: marxin at gcc dot gnu.org @ 2022-12-23 15:41 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108213

            Bug ID: 108213
           Summary: [[noreturn]] cannot be used after static keyword
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin at gcc dot gnu.org
                CC: jsm28 at gcc dot gnu.org
  Target Milestone: ---

I noticed that in timezone package:

$ cat zic.i && gcc-12 zic.i -c
static _Noreturn void
time_overflow(void)
{
  __builtin_abort ();
}

$ cat zic.i && gcc-12 zic.i -c
static [[noreturn]] void
time_overflow(void)
{
  __builtin_abort ();
}
zic.i:1:1: warning: ‘noreturn’ attribute ignored [-Wattributes]
    1 | static [[noreturn]] void
      | ^~~~~~
zic.i:1:21: error: expected identifier or ‘(’ before ‘void’
    1 | static [[noreturn]] void
      |                     ^~~~

Is it really an invalid construction?

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-12-27 10:14 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-12-23 15:41 [Bug c/108213] New: [[noreturn]] cannot be used after static keyword marxin at gcc dot gnu.org
2022-12-23 15:46 ` [Bug c/108213] " pinskia at gcc dot gnu.org
2022-12-27 10:14 ` marxin at gcc dot gnu.org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).