From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 0CDAC3857B93; Thu, 26 Oct 2023 08:26:39 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0CDAC3857B93
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1698308800;
	bh=fKIMW22hSBj0PG2s1KnDog+aocYYMG3JlGDQ5le0GV8=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=F7ZxbVC0XXe/clj2NWB0nNTHxgpl5cE8fPFhb4EBzdzQ/rK66pVQ76qCtrB/9ifhQ
	 QfnoOQel6I/A8wfl2bQyLU7smY0J1lY8BW1m/vtYsvHN48OYi/YY+xUNBdFPSwnEj4
	 EJ36u8sebzrWUHEYGI6+CnYzbhuXGr8jdPgy6hLA=
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/104625] ICE in fixup_array_ref, at
 fortran/resolve.cc:9275 since r10-2912-g70570ec192745095
Date: Thu, 26 Oct 2023 08:26:38 +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: pault at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-104625-4-kPae5ACsxJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-104625-4@http.gcc.gnu.org/bugzilla/>
References: <bug-104625-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D104625

--- Comment #8 from Paul Thomas <pault at gcc dot gnu.org> ---
(In reply to anlauf from comment #6)
> Steve Lionel of Intel confirmed that the code is valid, and that if X is
> polymorphic, so is (X):
>=20
> community.intel.com/t5/Intel-Fortran-Compiler/SELECT-TYPE-statement-and-
> parenthesized-selector/m-p/1537256#M168843

Indeed:

"R1105: selector is expr or variable" is totally unambiguous.

I will post the latest version of the patch at end-of-play today. I have de=
alt
with nested parentheses but find that array references to 'z' in the origin=
al
testcase are generating "unclassifiable statement" errors.

I have also corrected the error message generated when 'z' is put in an
assignment context from, "=E2=80=98z=E2=80=99 at (1) associated to vector-i=
ndexed target cannot
be used in a variable definition context (assignment)" to "=E2=80=98z=E2=80=
=99 at (1)
associated to expression cannot be used in a variable definition context
(assignment)", simply by checking for vector-indexing at expr.cc:6477.

Cheers

Paul=