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++/109357] [12 Regression] internal compiler error in cp/constexpr.cc:1685 Date: Tue, 18 Apr 2023 20:46:48 +0000 [thread overview] Message-ID: <bug-109357-4-j02wZSNdlV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109357-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109357 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:618b90f5688fa7c0923a3e07a0741c6ede0e6e4e commit r12-9445-g618b90f5688fa7c0923a3e07a0741c6ede0e6e4e Author: Jason Merrill <jason@redhat.com> Date: Fri Apr 14 22:40:43 2023 -0400 c++: constexpr aggregate destruction [PR109357] We were assuming that the result of evaluation of TARGET_EXPR_INITIAL would always be the new value of the temporary, but that's not necessarily true when the initializer is complex (i.e. target_expr_needs_replace). In that case evaluating the initializer initializes the temporary as a side-effect. PR c++/109357 gcc/cp/ChangeLog: * constexpr.cc (cxx_eval_constant_expression) [TARGET_EXPR]: Check for complex initializer. gcc/testsuite/ChangeLog: * g++.dg/cpp2a/constexpr-dtor15.C: New test.
prev parent reply other threads:[~2023-04-18 20:46 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-31 10:47 [Bug c++/109357] New: GCC 13.0.1: " kgledits at cisco dot com 2023-03-31 17:00 ` [Bug c++/109357] [12/13 Regression] " xry111 at gcc dot gnu.org 2023-03-31 17:11 ` jakub at gcc dot gnu.org 2023-04-15 2:25 ` jason at gcc dot gnu.org 2023-04-15 16:35 ` cvs-commit at gcc dot gnu.org 2023-04-18 20:46 ` [Bug c++/109357] [12 " jason at gcc dot gnu.org 2023-04-18 20:46 ` cvs-commit at gcc dot gnu.org [this message]
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-109357-4-j02wZSNdlV@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).