public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sbergman at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/103991] New: Bogus -Wreturn-type with constexpr if and local var with destructor
Date: Wed, 12 Jan 2022 13:56:27 +0000	[thread overview]
Message-ID: <bug-103991-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 103991
           Summary: Bogus -Wreturn-type with constexpr if and local var
                    with destructor
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: sbergman at redhat dot com
  Target Milestone: ---

Apparently a recent regression on GCC trunk:

> $ cat test.cc
> struct S { ~S(); };
> int f() {
>     S s;
>     if constexpr (true) return 0;
>     else return 0;
> }

> $ g++ -c test.cc
> test.cc: In function ‘int f()’:
> test.cc:6:1: warning: control reaches end of non-void function [-Wreturn-type]
>     6 | }
>       | ^

             reply	other threads:[~2022-01-12 13:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12 13:56 sbergman at redhat dot com [this message]
2022-01-12 14:03 ` [Bug c++/103991] [12 Regression] " jakub at gcc dot gnu.org
2022-01-12 16:04 ` jakub at gcc dot gnu.org
2022-01-12 16:06 ` jakub at gcc dot gnu.org
2022-01-12 16:33 ` jakub at gcc dot gnu.org
2022-01-12 16:47 ` jakub at gcc dot gnu.org
2022-01-12 16:58 ` jakub at gcc dot gnu.org
2022-01-12 19:42 ` rguenther at suse dot de
2022-01-12 20:02 ` jakub at gcc dot gnu.org
2022-01-14 11:10 ` cvs-commit at gcc dot gnu.org
2022-01-17 17:48 ` 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-103991-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).