From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 23A5E385840D; Thu,  4 Apr 2024 20:55:51 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 23A5E385840D
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1712264151;
	bh=EFPcBl+Xjl+euSnCBQInUdRA5RzsOnb3nDDhNGRLIjE=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=rr863CyFCkUy532w9kVPieTnYFnOgte4r1vfnLWU0URlHhy2lonQyPrtTHEKaHHhk
	 ka7XbxBHRSwZIpFKwi9QI5RDrsGi4T4MOMeL1ZioQZA7BVpCrCdOSjwT/cS83YPQEt
	 +kN7r0ThKUVQmuS7uRE7IiPrP2anTHAQy/VuEyb8=
From: "kargls at comcast dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/89925] [11/12/13/14 Regression] Wrong array bounds from
 ALLOCATE with SOURCE or MOLD
Date: Thu, 04 Apr 2024 20:55:50 +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: kargls at comcast dot net
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 11.5
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-89925-4-IOCTXIqRbN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89925-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89925-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D89925

--- Comment #14 from kargls at comcast dot net ---
(In reply to anlauf from comment #13)
> Original testcase is fixed for allocate with mold as well as for allocate
> with source, and some test coverage is in r12-5767.
>=20
> There are remaining issues for allocatable character arrays, but these
> are tracked elsewhere, e.g. pr113793.
>=20
> I suggest to close this one with target milestone 12.x

Seems like a good idea.  Do you believe that original
testcase should be converted to a testcase and committed?=