public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "f.heckenbach@fh-soft.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/104494] New: -Wsuggest-attribute=noreturn catch 22
Date: Thu, 10 Feb 2022 21:59:53 +0000	[thread overview]
Message-ID: <bug-104494-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 104494
           Summary: -Wsuggest-attribute=noreturn catch 22
           Product: gcc
           Version: 11.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: f.heckenbach@fh-soft.de
  Target Milestone: ---

% cat test3.cpp 
void f ()
{
  [] { throw 42; } ();
}
% g++ -Wsuggest-attribute=noreturn -O3 test3.cpp -c
test3.cpp: In function 'void f()':
test3.cpp:1:6: warning: function might be candidate for attribute 'noreturn'
[-Wsuggest-attribute=noreturn]

% cat test3.cpp 
[[noreturn]] void f ()
{
  [] { throw 42; } ();
}
% g++ -Wsuggest-attribute=noreturn -O3 test3.cpp -c
test3.cpp: In function 'void f()':
test3.cpp:4:1: warning: 'noreturn' function does return

clang also gives the latter warning (it doesn't seem to have the
-Wsuggest-attribute=noreturn flag), so maybe something in the standard does
make f unsuitable for [[noreturn]]. But then -Wsuggest-attribute=noreturn
should not suggest so.

             reply	other threads:[~2022-02-10 21:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 21:59 f.heckenbach@fh-soft.de [this message]
2022-02-11  9:16 ` [Bug c++/104494] " rguenth 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-104494-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: link
Be 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).