public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/100068] inconsistent handling of noreturn on nested function declarations Date: Tue, 13 Apr 2021 19:10:40 +0000 [thread overview] Message-ID: <bug-100068-4-hf0mbyWYqW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100068-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100068 Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|wrong-code |diagnostic --- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> --- On second thought, and after reading what C and C++ say about noreturn, I don't think it's wrong to emit just one call to either g0() or g1() in the test case. C in particular specifies that: A function declared with a _Noreturn function specifier shall not return to its caller. so declaring a function _Noreturn once is enough to grant the permission to eliminate subsequent code regardless of any intervening redeclarations of the function. Let me change the Keywords from wrong-code to missing diagnostic.
next prev parent reply other threads:[~2021-04-13 19:10 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-13 18:47 [Bug c/100068] New: " msebor at gcc dot gnu.org 2021-04-13 18:53 ` [Bug c/100068] " msebor at gcc dot gnu.org 2021-04-13 19:10 ` msebor at gcc dot gnu.org [this message] 2021-04-13 20:05 ` pinskia at gcc dot gnu.org 2021-04-13 21:43 ` msebor 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-100068-4-hf0mbyWYqW@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).