public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/113674] [11/12/13/14 Regression] [[____attr____]] causes internal compiler error: in decl_attributes, at attribs.cc:776 Date: Wed, 31 Jan 2024 18:40:53 +0000 [thread overview] Message-ID: <bug-113674-4-G07ZybeoAg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113674-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113674 --- Comment #5 from Joseph S. Myers <jsm28 at gcc dot gnu.org> --- C supports _Noreturn (and thus ___Noreturn__) as an attribute name, so that code with "#define noreturn _Noreturn" (probably from stdnoreturn.h) works with C23 [[noreturn]].
next prev parent reply other threads:[~2024-01-31 18:40 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-30 21:44 [Bug c++/113674] New: " mpolacek at gcc dot gnu.org 2024-01-30 21:46 ` [Bug c++/113674] [11/12/13/14 Regression] " mpolacek at gcc dot gnu.org 2024-01-31 8:21 ` rguenth at gcc dot gnu.org 2024-01-31 16:06 ` mpolacek at gcc dot gnu.org 2024-01-31 16:38 ` jakub at gcc dot gnu.org 2024-01-31 16:54 ` mpolacek at gcc dot gnu.org 2024-01-31 18:40 ` jsm28 at gcc dot gnu.org [this message] 2024-02-12 12:23 ` jakub at gcc dot gnu.org 2024-02-12 19:45 ` cvs-commit at gcc dot gnu.org 2024-02-12 19:48 ` [Bug c++/113674] [11/12/13 " jakub at gcc dot gnu.org 2024-03-02 0:38 ` cvs-commit at gcc dot gnu.org 2024-03-04 12:08 ` [Bug c++/113674] [11/12 " jakub at gcc dot gnu.org 2024-06-11 10:37 ` cvs-commit at gcc dot gnu.org 2024-06-11 10:50 ` [Bug c++/113674] [11 " jakub at gcc dot gnu.org 2024-06-20 13:22 ` cvs-commit at gcc dot gnu.org 2024-06-20 13:38 ` jakub 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-113674-4-G07ZybeoAg@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).