From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 697693858D20; Mon, 1 Apr 2024 20:42:36 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 697693858D20 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1712004156; bh=/80wJM6eNAE0s/WVeaRr9fgd/Lmh5W0RB1sBpjjLwpk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Gc94YtYmqNOBT62KwaiXEt01BpXQ87Ht9FZJPmsB1vunpptWO7eUAjIKD1HgNWGF1 TX9ekBYcoUXgz+ZyBh9ZNsyqiVY/YM0BUMjNdBWXBDNLrGFHhwzEtVZTpv3iVZ7Fhl m9bSERFpdwT4xzcs9sn4VuSNQT5HDvi6XGB07IRo= From: "anlauf at gcc dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: ice-on-invalid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: anlauf at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P4 X-Bugzilla-Assigned-To: anlauf at gcc dot gnu.org X-Bugzilla-Target-Milestone: 11.5 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D106987 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, >=20 > 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?=