From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 09FA13858C30; Fri, 3 Feb 2023 20:03:08 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 09FA13858C30 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1675454589; bh=Wsh/a2V4pSlkHVrlq6htGp6oXTbqj5IZI6+pDUa44W0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=WgcWE2qpDhj1RY1TRovPzgoRJ0ORhO7dC5FeFUzYoLqw5+OMc6scSc2u9r0AN0gS8 yMWPxDc3+MhLUqOw03uxTgyFDgnnXylvoYPbLUk8dIVnCdiddlc2S6dS/98d78Gp1y aVw9PFd/fr8V/YTP4BY3rfCbCqlOKEHLFNgROSoo= From: "kargl at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/89925] [10/11/12/13 Regression] Wrong array bounds from ALLOCATE with SOURCE or MOLD Date: Fri, 03 Feb 2023 20:03:08 +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: 9.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: kargl at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P4 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 10.5 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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=3D89925 kargl at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kargl at gcc dot gnu.org --- Comment #11 from kargl at gcc dot gnu.org --- (In reply to Tobias Burnus from comment #10) > I think that could be the commit > r12-5767-g6262e3a22b3d86afc116480bc59a7bb30b0cfd40 > "fortran: Fix setting of array lower bound for named arrays" >=20 > but I have not checked more deeply. I can confirm that your patch in r12-5767-yada-yada fixed this bug. Your patch included two testcases. Do you think that Neil's code should be converted to a new testcase or do your testcases cover this issue. Neil, sorry it took so long to get a fix.=