public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/102620] [12 Regression] ICE in gfc_get_array_span, at fortran/trans-array.c:865 since r12-1233-gd514626ee2566c68
Date: Thu, 25 Apr 2024 18:32:25 +0000 [thread overview]
Message-ID: <bug-102620-4-U2bA9Phprr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102620-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102620
--- Comment #10 from anlauf at gcc dot gnu.org ---
(In reply to Paul Thomas from comment #9)
> (In reply to anlauf from comment #8)
> > I get the same behavior at r13-8559 as 14-mainline. There seems to be
> > another commit that fixed it independently.
> >
> > Removing 13-branch from the regression list.
>
> Mark as fixed or backport fixes?
Either I did something wrong, or the bug reappeared on 13-branch...
Anyway, I tried backporting Andre's patch to 13- and 12-branch.
Works fine and regtests fine.
How to proceed?
I can push those changes, so that we are finally done with this PR.
next prev parent reply other threads:[~2024-04-25 18:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 18:34 [Bug fortran/102620] New: [12 Regression] ICE in gfc_get_array_span, at fortran/trans-array.c:865 gscfq@t-online.de
2021-10-05 18:35 ` [Bug fortran/102620] " gscfq@t-online.de
2021-10-05 19:22 ` anlauf at gcc dot gnu.org
2021-10-06 8:41 ` rguenth at gcc dot gnu.org
2021-10-11 8:26 ` [Bug fortran/102620] [12 Regression] ICE in gfc_get_array_span, at fortran/trans-array.c:865 since r12-1233-gd514626ee2566c68 marxin at gcc dot gnu.org
2022-05-06 8:31 ` [Bug fortran/102620] [12/13 " jakub at gcc dot gnu.org
2023-05-08 12:22 ` [Bug fortran/102620] [12/13/14 " rguenth at gcc dot gnu.org
2023-08-21 20:58 ` anlauf at gcc dot gnu.org
2024-04-02 20:28 ` [Bug fortran/102620] [12 " anlauf at gcc dot gnu.org
2024-04-25 6:30 ` pault at gcc dot gnu.org
2024-04-25 18:32 ` anlauf at gcc dot gnu.org [this message]
2024-04-26 5:24 ` pault at gcc dot gnu.org
2024-04-26 18:36 ` anlauf at gcc dot gnu.org
2024-04-26 19:24 ` anlauf 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-102620-4-U2bA9Phprr@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: link
Be 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).