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++/101072] [12 Regression] ICE in build_target_expr_with_type, at cp/tree.c:845 since r11-5681-gd9288bd28e24c755 Date: Wed, 26 Jan 2022 19:27:45 +0000 [thread overview] Message-ID: <bug-101072-4-omifsO0YVY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101072-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101072 --- Comment #7 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:9bf217920457f2e2d46b601f24721780a20a031b commit r12-6883-g9bf217920457f2e2d46b601f24721780a20a031b Author: Jason Merrill <jason@redhat.com> Date: Wed Jan 26 12:44:31 2022 -0500 c++: vector compound literal [PR104206] My patch for PR101072 removed the specific VECTOR_TYPE handling here, which broke pr72747-2.c on PPC; this patch restores it. PR c++/104206 PR c++/101072 gcc/cp/ChangeLog: * semantics.cc (finish_compound_literal): Restore VECTOR_TYPE check.
prev parent reply other threads:[~2022-01-26 19:27 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-14 17:23 [Bug c++/101072] New: [11/12 Regression] ICE in build_target_expr_with_type, at cp/tree.c:845 gscfq@t-online.de 2021-06-15 7:22 ` [Bug c++/101072] [11/12 Regression] ICE in build_target_expr_with_type, at cp/tree.c:845 since r11-5681-gd9288bd28e24c755 marxin at gcc dot gnu.org 2021-06-15 7:53 ` rguenth at gcc dot gnu.org 2021-07-07 21:38 ` jason at gcc dot gnu.org 2021-07-07 22:50 ` cvs-commit at gcc dot gnu.org 2021-07-07 22:50 ` [Bug c++/101072] [12 " jason at gcc dot gnu.org 2021-07-28 7:07 ` rguenth at gcc dot gnu.org 2021-12-28 23:48 ` pinskia at gcc dot gnu.org 2022-01-23 3:19 ` cvs-commit at gcc dot gnu.org 2022-01-23 22:33 ` jason at gcc dot gnu.org 2022-01-26 19:27 ` 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-101072-4-omifsO0YVY@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).