From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B56913858291; Sun, 28 Aug 2022 20:16:44 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B56913858291 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1661717804; bh=hLEwAheSL8UV011Z/lmGB8E4TeKk5uZY71RWGvH7+lk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=uvR/i30unAEiSdwEw0LLJiXKBnYkHqkabcqyvITCD+srAuNRQTWrRTb109bFOVFu3 gVgkpkWKWltdV6e9LaOOGjVlTu76hqhxKpRH4/5HLtlonprkusNNhHFBasa5Si2ib8 pSyrIXz5XsBx5z4qfmFcf4bFGL7VnsQ3szLOJMW4= From: "anlauf at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/93482] ICE in gfc_resolve_character_array_constructor, at fortran/array.c:2096 Date: Sun, 28 Aug 2022 20:16:44 +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: 10.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: anlauf at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution 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=3D93482 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution|--- |FIXED --- Comment #5 from anlauf at gcc dot gnu.org --- (In reply to anlauf from comment #3) > Seems to have been fixed on mainline, and backported to 11- and 10-branch. > Likely a duplicate. Some issues with zero-sized constructors as in comment#2 have been fixed for pr103692. There have been fixes for other issues with constructors, including nested constructors. I believe there is sufficient coverage for trivial cases like those in this PR, and it would be beneficial to have a clean, separate PR for remaining problems. Closing this one. Thanks for the report!=