public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/93956] Wrong array creation with p => array_dt(1:n)%component Date: Wed, 11 Mar 2020 12:04:57 +0000 [thread overview] Message-ID: <bug-93956-4-9Loc37Mki9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-93956-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93956 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marxin at gcc dot gnu.org --- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> --- commit r10-7115-gdf15a82804e1f7f4a7432670b33387779de46549 Author: Jason Merrill <jason@redhat.com> Date: Tue Mar 10 17:51:46 2020 -0400 c++: Fix ICE with omitted template args [PR93956]. reshape_init only wants to work on BRACE_ENCLOSED_INITIALIZER_P, i.e. raw initializer lists, and here was getting a CONSTRUCTOR that had already been processed for type A<int>. maybe_aggr_guide should also use that test. gcc/cp/ChangeLog 2020-03-10 Jason Merrill <jason@redhat.com> PR c++/93956 * pt.c (maybe_aggr_guide): Check BRACE_ENCLOSED_INITIALIZER_P.
next parent reply other threads:[~2020-03-11 12:04 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-93956-4@http.gcc.gnu.org/bugzilla/> 2020-03-11 12:04 ` marxin at gcc dot gnu.org [this message] 2020-04-14 17:16 ` tkoenig at gcc dot gnu.org 2020-04-20 5:26 ` mscfd at gmx dot net 2020-04-20 14:36 ` tkoenig at gcc dot gnu.org 2020-04-20 16:08 ` tkoenig at gcc dot gnu.org 2020-04-20 18:42 ` tkoenig at gcc dot gnu.org 2020-04-21 18:48 ` tkoenig at gcc dot gnu.org 2020-04-23 18:31 ` cvs-commit at gcc dot gnu.org 2020-04-24 6:23 ` cvs-commit at gcc dot gnu.org 2020-04-24 7:27 ` cvs-commit at gcc dot gnu.org 2020-04-24 7:28 ` tkoenig at gcc dot gnu.org 2020-04-24 7:28 ` tkoenig at gcc dot gnu.org 2020-04-26 12:52 ` cvs-commit at gcc dot gnu.org 2020-04-27 21:51 ` cvs-commit at gcc dot gnu.org 2020-04-27 21:53 ` tkoenig at gcc dot gnu.org 2020-04-28 16:23 ` pault at gcc dot gnu.org 2020-05-01 12:53 ` cvs-commit at gcc dot gnu.org 2020-05-01 12:55 ` cvs-commit at gcc dot gnu.org 2020-05-21 10:42 ` tkoenig at gcc dot gnu.org 2021-04-16 16:22 ` tkoenig 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-93956-4-9Loc37Mki9@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).