From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 740CD3858280; Sun, 6 Aug 2023 00:54:25 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 740CD3858280 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1691283265; bh=/d65quomepqAE+sLs9vw19X9qRXcvLeNYJrbXmABY+s=; h=From:To:Subject:Date:In-Reply-To:References:From; b=xdKWiv82vF5etzHUqlyMLRpygZFclx7zU+qIxlQySseuovVZOgO5exMWZKcvDZNVi yhQFG4LHCL6rXKbZoUEPLJCqZYN/C876FMMfVcmOGJJ3ppIr6rBSbcTiXWFBp6Kh9x o1YpQQmtjAyaixUPkb8uho7/XWhFKhebT2Rm3d/o= From: "cvs-commit at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/107397] [11/12 Regression] ICE in gfc_arith_plus, at fortran/arith.cc:654 Date: Sun, 06 Aug 2023 00:54:24 +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, patch X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P4 X-Bugzilla-Assigned-To: jvdelisle at gcc dot gnu.org X-Bugzilla-Target-Milestone: 11.5 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=3D107397 --- Comment #19 from CVS Commits --- The releases/gcc-11 branch has been updated by Jerry DeLisle : https://gcc.gnu.org/g:088d907f69901f8d7e40ea099ccb5e42999c472c commit r11-10939-g088d907f69901f8d7e40ea099ccb5e42999c472c Author: Jakub Jelinek Date: Mon Dec 19 11:24:55 2022 +0100 testsuite: Fix up pr107397.f90 test [PR107397] The pr107397.f90 test FAILs for me, one problem was that the added diagnostics has an indefinite article before BOZ, but the test dg-error didn't. The other problem was that on the other dg-error there was no space between the string and closing }, so it was completely ignored and the error was an excess error. 2022-12-19 Jakub Jelinek PR fortran/107397 * gfortran.dg/pr107397.f90: Adjust expected diagnostic wording = and add space between dg-error string and closing }. (cherry picked from commit 03fb35f8753d87148b29b3f34b6154abe7db4c41)=