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 C19FB3858027; Fri,  7 Oct 2022 21:02:17 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C19FB3858027
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1665176537;
	bh=v+z4YJW9EbxMqKhZRXCtI1y0lXHSucBXWCCFytMvblI=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=G1zGr8CAeA2EfaYDtfns+Y6DUHeBc8szJVDjK+AjVardyPnyTtdxfrLYOIBTqcq1b
	 WfwYmyuGBAbgBB2FQcHXspZkD2WxyVy/z4tPdpcltkH6TbbF4XR9o5QadHQCLcKY9I
	 GTRcKxEd9JfvzGAXb4HbaP9bBqH1sg1GArGAy6SE=
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66409] Reporting ambiguous interface when overloading
 assignment with polymorphic array
Date: Fri, 07 Oct 2022 21:02:17 +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: 4.9.2
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution: 
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: 
Message-ID: <bug-66409-4-gNiRc6e571@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66409-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66409-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=3D66409

--- Comment #8 from Steve Kargl <sgk at troutmask dot apl.washington.edu> -=
--
On Fri, Oct 07, 2022 at 08:42:51PM +0000, mikael at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D66409
>=20
> Mikael Morin <mikael at gcc dot gnu.org> changed:
>=20
>            What    |Removed                     |Added
> -------------------------------------------------------------------------=
---
>                  CC|                            |mikael at gcc dot gnu.org
>=20
> --- Comment #7 from Mikael Morin <mikael at gcc dot gnu.org> ---
> (In reply to anlauf from comment #6)
> > (In reply to Steve Kargl from comment #5)
> >=20
> > > Perhaps, someone, who cares about this bug, can point at the language=
 in
> > > the Fortran standard.
> >=20
> > I looked again at F2018 and couldn't find anything.
> >=20
>=20
> I think it's in 15.4.3.4.5 Restrictions on generic declarations.
> But it's too late for me to decipher what's written there.
>=20

   Two dummy arguments are distinguishable if

   =C2=B7 one is a procedure and the other is a data object,
   =C2=B7 they are both data objects or known to be functions,
     and neither is TKR compatible with the other,
   =C2=B7 one has the ALLOCATABLE attribute and the other has
     the POINTER attribute and not the INTENT (IN) attribute, or
   =C2=B7 one is a function with nonzero rank and the other is not
     known to be a function.

Bullet 2 is the TKR restriction.  Admittedly, 21-007.pdf:C1514 is
somewhat difficult to parse with the non-passed-object dummy data
object vs passed-object dummy data object language.=