From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E0FC43858D1E; Fri, 2 Sep 2022 19:04:36 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E0FC43858D1E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1662145476; bh=uSEWYYHRMrUzIEek4q5hsvcOcilyY/YearYM4JdYZlg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=b0SOSuY7TiGqudytnaE5bWo5Tyn9jZil4WW2WaS0CwyTgkTdLy8PA2scy0Kbagv5G D0d/wT58Snw0KVs1Kj82xfMK/5N0WYlzLtNRTG5OMPXZGVUeIpupcvUrvO9ZbhV5P8 G99NaCmRo1YaYqUdcFz/PmUtEj+zJY+ssNskIw7k= From: "mikael at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/105012] [12/13 Regression] wrf from SPECCPU2017 ICEs during LTO linking since r12-7692-g8db155ddf8cec9 Date: Fri, 02 Sep 2022 19:04:34 +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: 12.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: mikael at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P4 X-Bugzilla-Assigned-To: mikael at gcc dot gnu.org X-Bugzilla-Target-Milestone: 12.3 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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=3D105012 --- Comment #31 from Mikael Morin --- (In reply to Mikael Morin from comment #30) > (In reply to anlauf from comment #29) > >=20 > > but if your patch regtests fine then you should proceed. >=20 > Ok, let=E2=80=99s see how good it is. > Assigning. It seems to work, but trying to extend clobbering further, I uncovered a bug latent on master: PR106817. Maybe not that good an idea to extend clobbering further. :-(=