public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/103991] [12 Regression] Bogus -Wreturn-type with constexpr if and local var with destructor
Date: Wed, 12 Jan 2022 20:02:56 +0000 [thread overview]
Message-ID: <bug-103991-4-Tfbt7NXc7B@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103991-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103991
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to rguenther@suse.de from comment #7)
> > Now, as Richi's warning isn't in GCC 12, quickest/safest temporary fix would be
> > to revert to previous behavior for IF_STMT_CONSTEXPR_P and IF_STMT_CONSTEVAL_P,
> > if (IF_STMT_CONSTEVAL_P (stmt))
> > stmt = else_;
> > else if (IF_STMT_CONSTEXPR_P (stmt))
> > stmt = integer_nonzerop (cond) ? then_ ? else_;
> > else
> > stmt = build3 (COND_EXPR, void_type_node, cond, then_, else_);
>
> I agree that reverting for GCC 12 is the most reasonable thing with adding a
> Testcase
The above isn't a full reversion, it keeps the normal if (which isn't
problematic) as is and just reverts behavior for the special const{expr,eval}
ifs.
next prev parent reply other threads:[~2022-01-12 20:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 13:56 [Bug c++/103991] New: " sbergman at redhat dot com
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 [this message]
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-Tfbt7NXc7B@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).