public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109030] [13 Regression] checking ICE in cxx_eval_call_expression with aggregate initialization inside noexcept Date: Tue, 07 Mar 2023 15:14:07 +0000 [thread overview] Message-ID: <bug-109030-4-w2JnuWQKPS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109030-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109030 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>: https://gcc.gnu.org/g:e4692319fd5fc7d740436e8bb338f44cb8df6c58 commit r13-6526-ge4692319fd5fc7d740436e8bb338f44cb8df6c58 Author: Marek Polacek <polacek@redhat.com> Date: Mon Mar 6 18:06:39 2023 -0500 c++: noexcept and copy elision [PR109030] When processing a noexcept, constructors aren't elided: build_over_call has /* It's unsafe to elide the constructor when handling a noexcept-expression, it may evaluate to the wrong value (c++/53025). */ && (force_elide || cp_noexcept_operand == 0)) so the assert I added recently needs to be relaxed a little bit. PR c++/109030 gcc/cp/ChangeLog: * constexpr.cc (cxx_eval_call_expression): Relax assert. gcc/testsuite/ChangeLog: * g++.dg/cpp0x/noexcept77.C: New test.
next prev parent reply other threads:[~2023-03-07 15:14 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-05 19:34 [Bug c++/109030] New: " ppalka at gcc dot gnu.org 2023-03-05 19:36 ` [Bug c++/109030] [13 Regression] checking " ppalka at gcc dot gnu.org 2023-03-06 14:39 ` mpolacek at gcc dot gnu.org 2023-03-07 15:14 ` cvs-commit at gcc dot gnu.org [this message] 2023-03-07 15:15 ` mpolacek at gcc dot gnu.org 2023-03-16 18:47 ` cvs-commit 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-109030-4-w2JnuWQKPS@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).