public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/108213] New: [[noreturn]] cannot be used after static keyword Date: Fri, 23 Dec 2022 15:41:07 +0000 [thread overview] Message-ID: <bug-108213-4@http.gcc.gnu.org/bugzilla/> (raw) 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?
next reply other threads:[~2022-12-23 15:41 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-23 15:41 marxin at gcc dot gnu.org [this message] 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
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-108213-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).