From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B04B33858427; Fri, 26 Aug 2022 10:59:48 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B04B33858427 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1661511588; bh=diFWoqVGGH/7wJTOWzx3rnWRzDhPdxQf7JeG7G/Objg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=bYVxsN+HnPsZbqjowk/4bSPwTMiqml9sDXFnW43jEls6Rzktb1SQuIFboMYdLVwIk MMCPJ2v3HYZXaAjPsvgVEvKKeOXzLD0TYjcGDKFYbhwi0Qu2H0yclCzkEnV3ykzd6N diuvt15uJlJIXBqzv3HJteZT6lwi9tiCoiYjD1es= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/104430] [10 Regression] ICE in gfc_conv_component_ref, at fortran/trans-expr.cc:2742 since r9-3522-gd0477233215e37de Date: Fri, 26 Aug 2022 10:59:48 +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: 12.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: redi 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: 10.5 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=3D104430 --- Comment #7 from Jonathan Wakely --- The patch also fixes an ICE for this code, taken from https://stackoverflow.com/q/73498995/981959 program main integer, dimension(1:2) :: iii real, dimension(1:4,1:4,1:2) :: myArray associate(iix =3D> iii(1), iiy=3D> iii(2) ) forall( iix=3D1:4, iiy=3D1:4 ) myArray(iix,iiy,1) =3D iix + iiy myArray(iix,iiy,2) =3D (iix + iiy)*10 endforall end associate print *, myArray(:,:,1) print *, myArray(:,:,2) end program main I know nothing about Fortran, but it looks sufficiently different to me that maybe it's worth adding another test based on this code, so we don't regres= s. The question of whether to backport to gcc-10 or close this is still waiting for an answer too.=