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++/104084] [12 regression] Internal compiler error: tree check: expected target_expr, have compound_expr in build_new_1 since r12-6375-g6cd51207f5732b52 Date: Fri, 21 Jan 2022 20:18:23 +0000 [thread overview] Message-ID: <bug-104084-4-sN0JGBDmJx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104084-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104084 --- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:847a8301add0a316767878342c1367948835c181 commit r12-6808-g847a8301add0a316767878342c1367948835c181 Author: Jason Merrill <jason@redhat.com> Date: Fri Jan 21 12:49:03 2022 -0500 c++: class array new checking [PR104084] My patch for PR20040 made us stop exiting early from build_new_1 in cases of trivial initialization if there's a class operator delete; as a result, code later in the function needs to handle this case properly. PR c++/104084 PR c++/20040 gcc/cp/ChangeLog: * init.cc (build_new_1): Only pull out TARGET_EXPR_INITIAL if alloc_expr is a TARGET_EXPR. gcc/testsuite/ChangeLog: * g++.dg/init/new50.C: New test.
next prev parent reply other threads:[~2022-01-21 20:18 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-18 9:37 [Bug c++/104084] New: [12 regression] Internal compiler error: tree check: expected target_expr, have compound_expr in build_new_1 linux at carewolf dot com 2022-01-18 9:38 ` [Bug c++/104084] " marxin at gcc dot gnu.org 2022-01-18 9:44 ` linux at carewolf dot com 2022-01-18 9:48 ` linux at carewolf dot com 2022-01-18 9:50 ` linux at carewolf dot com 2022-01-18 9:50 ` rguenth at gcc dot gnu.org 2022-01-18 10:00 ` marxin at gcc dot gnu.org 2022-01-18 11:56 ` [Bug c++/104084] [12 regression] Internal compiler error: tree check: expected target_expr, have compound_expr in build_new_1 since r12-6375-g6cd51207f5732b52 marxin at gcc dot gnu.org 2022-01-18 13:26 ` jakub at gcc dot gnu.org 2022-01-21 17:43 ` jason at gcc dot gnu.org 2022-01-21 20:18 ` cvs-commit at gcc dot gnu.org [this message] 2022-01-21 20:18 ` jason 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-104084-4-sN0JGBDmJx@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).