public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/104570] [12 Regression] ICE in gfc_conv_scalarized_array_ref, at fortran/trans-array.cc:3681 since r12-7217-g57da34939703a6e6 Date: Sun, 27 Feb 2022 20:03:12 +0000 [thread overview] Message-ID: <bug-104570-4-rgz84x0XAj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104570-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104570 Mikael Morin <mikael at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |mikael at gcc dot gnu.org Status|NEW |ASSIGNED --- Comment #3 from Mikael Morin <mikael at gcc dot gnu.org> --- Created attachment 52521 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52521&action=edit Draft patch, regtests cleanly My bug, I guess. Here is a (very ad hoc) fix. I have yet to see how much of it is really necessary, and whether I want this rather than reverting the regressing revision.
next prev parent reply other threads:[~2022-02-27 20:03 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-16 17:32 [Bug fortran/104570] New: [12 Regression] ICE in gfc_conv_scalarized_array_ref, at fortran/trans-array.cc:3681 gscfq@t-online.de 2022-02-16 17:33 ` [Bug fortran/104570] " gscfq@t-online.de 2022-02-17 10:08 ` rguenth at gcc dot gnu.org 2022-02-24 13:26 ` [Bug fortran/104570] [12 Regression] ICE in gfc_conv_scalarized_array_ref, at fortran/trans-array.cc:3681 since r12-7217-g57da34939703a6e6 marxin at gcc dot gnu.org 2022-02-27 20:03 ` mikael at gcc dot gnu.org [this message] 2022-03-19 20:17 ` cvs-commit at gcc dot gnu.org 2022-03-20 17:17 ` mikael at gcc dot gnu.org 2022-04-10 18:48 ` cvs-commit at gcc dot gnu.org 2022-04-24 16:54 ` cvs-commit at gcc dot gnu.org 2022-05-09 11:22 ` 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-104570-4-rgz84x0XAj@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).