From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C8C493858C39; Thu, 13 Oct 2022 19:26:09 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C8C493858C39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1665689169; bh=Yfw9E7m6LrNwHBKqO0yJIikN6ogM+bc+rqtCvpTHA8g=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Pn4XT+OESu2bN8JTxI+6+gOdCNrrfpTHH952J788k/9CqE8+aIjk+1gp7qlFKLwqd a3YYM50u5Qx+3jiEn/a0xLU3EVsDAMSjzB4v6GxUBdAAFsEt0fsMwC06BZ5FoDM6eE NWt5OlUwPLTaVeJSRDI+zaVqY0UdWnvCv/ANNKKY= From: "sgk at troutmask dot apl.washington.edu" 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:26:09 +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: sgk at troutmask dot apl.washington.edu 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 #10 from Steve Kargl = --- On Thu, Oct 13, 2022 at 07:09:28PM +0000, anlauf at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D93483 >=20 > --- Comment #9 from anlauf at gcc dot gnu.org --- > (In reply to Steve Kargl from comment #8) > > If regtesting complete ok, >=20 > This is the case. >=20 > > and Mikael doesn't find any additional problems. Please commit. >=20 > The only thing I was fearing^Wexpecting is that he finds a better place > for the fix. >=20 > 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. >=20 > Do you know the history of this? >=20 Unfortunately, no. I believe g95 came into GCC as gfortran in the tree-ssa branch (under cvs). At one time, one could check on-line the branches under subversion. I cannot find a tree-ssa branch under git with the on-line repository. I suspect this dates back to g95,=20 and falls under the development where one assumes only correctly written standard conforming Fortran is fed into gfortran.=