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: Tue, 02 Apr 2024 17:38:35 +0000	[thread overview]
Message-ID: <bug-106987-4-AU0BadQDss@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|ASSIGNED                    |RESOLVED
   Target Milestone|11.5                        |13.3
         Resolution|---                         |FIXED

--- Comment #10 from anlauf at gcc dot gnu.org ---
(In reply to paul.richard.thomas@gmail.com from comment #8)
> Hi Harald,
> 
> After a lot of messing around, I managed to backport the patch; essentially
> by hand. However, two of the  testcases ICEd in trans-array.cc and so there
> were obviously dependences that I had missed.
> 
> I will not be backporting r14-1629, if for no other reason than it is not a
> regression but also because the amount of work that would be involved
> doesn't warrant it. It's a pity that I didn't keep 13-branch up to speed
> with mainline on the associate fixes but we will just have to live with it
> now.

Hi Paul,

no problem, I manually removed the conflict and pushed after regtesting.
Thanks for trying!

As I said before, I will close this one as fixed with target milestone 13.3,
as it does not make sense to try to backport all needed dependencies to 12,
and this one is an ICE-on-invalid.

@Gerhard: thanks for the report!

      parent reply	other threads:[~2024-04-02 17:38 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
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 [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-106987-4-AU0BadQDss@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).