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/106987] [11/12/13/14 Regression] ICE in simplify_intrinsic_op, at fortran/expr.cc:1305
Date: Mon, 01 Apr 2024 20:42:35 +0000 [thread overview]
Message-ID: <bug-106987-4-wHbuuJ6Y6O@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106987-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106987
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #6 from anlauf at gcc dot gnu.org ---
(In reply to Paul Thomas from comment #5)
> Hi Harald,
>
> I am pinning this one on you since it needs backporting to 13-branch, at
> least. It also keeps the audit trail clean.
Hi Paul,
this one is at the top of my backport list.
It depends on backporting r14-8902 (mine), and has weak conflict if
r14-1629 (yours) is not backported, as testcase gfortran.dg/pr99350.f90
was introduced in that commit.
I could amend backporting the fix for the current PR as well as r14-8902
to 13-branch by removing the changes to pr99350.f90 from the backport.
That is likely the most simple solution, as backporting r14-1629 might
introduce regressions.
Nevertheless, the current fixes can only be backported to 13-branch,
as some of the infrastructure changes for better error recovery after
arithmetic errors and when array ctors are involved are to risky to
backport to 12-branch.
What do you think?
next prev parent reply other threads:[~2024-04-01 20:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 17:37 [Bug fortran/106987] New: [10/11/12/13 " gscfq@t-online.de
2022-09-20 17:38 ` [Bug fortran/106987] " gscfq@t-online.de
2022-09-20 18:54 ` anlauf at gcc dot gnu.org
2022-09-21 7:50 ` rguenth at gcc dot gnu.org
2023-07-07 10:44 ` [Bug fortran/106987] [11/12/13/14 " rguenth at gcc dot gnu.org
2024-03-06 16:57 ` cvs-commit at gcc dot gnu.org
2024-03-31 12:19 ` pault at gcc dot gnu.org
2024-04-01 20:42 ` anlauf at gcc dot gnu.org [this message]
2024-04-02 13:32 ` paul.richard.thomas at gmail dot com
2024-04-02 14:40 ` paul.richard.thomas at gmail dot com
2024-04-02 17:07 ` cvs-commit at gcc dot gnu.org
2024-04-02 17:38 ` 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-106987-4-wHbuuJ6Y6O@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).