From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 8B9973858C56; Thu, 4 Apr 2024 20:15:33 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8B9973858C56 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1712261733; bh=rZRZwL0Fv/QVOZow3mDuw2RIeRM1Lpgg3SuXtx7bSoU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=o5rQGdIjVhp7aL1JI306Pq9KDM7WEP3X6Ovw/A4ydkBaEw41i+vanlf/Ar86Jc2FE xDNfZXQb1VJMHMMmztTEPUw+3GMT6kcoYVpuTeCL4kEg/3tNBhyTj09CSXIw7SHID7 oguIdn7YPGeHVRYW0fm+3aQUJRqZitlbGNE1qsMc= From: "anlauf at gcc dot 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:15:32 +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: anlauf at gcc dot gnu.org 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: cf_known_to_work cf_known_to_fail 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=3D89925 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |12.3.0, 13.2.1, 14.0 Known to fail| |10.5.0, 11.4.1 Status|NEW |WAITING --- Comment #13 from anlauf at gcc dot gnu.org --- Original testcase is fixed for allocate with mold as well as for allocate with source, and some test coverage is in r12-5767. There are remaining issues for allocatable character arrays, but these are tracked elsewhere, e.g. pr113793. I suggest to close this one with target milestone 12.x=