public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105321] [9/10/11/12 Regression] "non-constant condition" issued for function containing a short-circuited unevaluated non-constant expression Date: Wed, 20 Apr 2022 19:59:51 +0000 [thread overview] Message-ID: <bug-105321-4-9AW5lnB6mP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105321-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105321 Marek Polacek <mpolacek at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 |P2 Summary|"non-constant condition" |[9/10/11/12 Regression] |issued for function |"non-constant condition" |containing a |issued for function |short-circuited unevaluated |containing a |non-constant expression |short-circuited unevaluated | |non-constant expression Target Milestone|--- |9.5 --- Comment #5 from Marek Polacek <mpolacek at gcc dot gnu.org> --- It's a regression, this worked with GCC 4.9.4. So the fix should be suitable for GCC 12 still.
next prev parent reply other threads:[~2022-04-20 19:59 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-20 18:47 [Bug c++/105321] New: " bekenn at gmail dot com 2022-04-20 19:10 ` [Bug c++/105321] " mpolacek at gcc dot gnu.org 2022-04-20 19:45 ` mpolacek at gcc dot gnu.org 2022-04-20 19:48 ` mpolacek at gcc dot gnu.org 2022-04-20 19:55 ` mpolacek at gcc dot gnu.org 2022-04-20 19:59 ` mpolacek at gcc dot gnu.org [this message] 2022-04-21 14:18 ` [Bug c++/105321] [9/10/11/12 Regression] " cvs-commit at gcc dot gnu.org 2022-04-21 15:39 ` [Bug c++/105321] [9/10/11 " mpolacek at gcc dot gnu.org 2022-04-21 17:00 ` bekenn at gmail dot com 2022-04-22 21:01 ` cvs-commit at gcc dot gnu.org 2022-04-22 21:01 ` mpolacek 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-105321-4-9AW5lnB6mP@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).