From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9D22E3858C55; Thu, 13 Oct 2022 19:09:29 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9D22E3858C55 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1665688169; bh=nWshTTi0D5fbWtFKgjbK9BU7KUHNzeEciF3tFKM4O0A=; h=From:To:Subject:Date:In-Reply-To:References:From; b=j+A52juQlZvn35wzJvwkV+cUyQ0Qx+rWUjjW/Up8YxzVcOe6kF5tDzSs+dlm68/Su 3D05OUPe659C/klyc4ojnrD5IyaGZFET39EF23gVP+Iyyv7Srw7f3foHBFXsxjXe+J wCleW8fhJFy5IEkWRfq2czghjgTGggsK0oU+uil8= From: "anlauf at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/93483] ICE in gfc_constructor_copy, at fortran/constructor.c:103 Date: Thu, 13 Oct 2022 19:09:28 +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: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P4 X-Bugzilla-Assigned-To: anlauf at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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=3D93483 --- Comment #9 from anlauf at gcc dot gnu.org --- (In reply to Steve Kargl from comment #8) > If regtesting complete ok, This is the case. > and Mikael doesn't find any additional problems. Please commit. The only thing I was fearing^Wexpecting is that he finds a better place for the fix. When varying various related testcases, one encounters from time to time the error "Array operands are incommensurate" (ARITH_INCOMMENSURATE). This seems to go back all the way to the beginnings of gfortran (r0-58166), and there is no helpful commit message. However, this error message can lead to confusion, and there are related PRs. Do you know the history of this?=