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 61F7D38582B7; Sat,  8 Oct 2022 16:02:07 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 61F7D38582B7
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1665244927;
	bh=1Qq4youtblvZFl8qbIRWYRD0cSraG4UfoZtlSye5KhE=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Lbg57fVs0nDt4dz4nDGsmIPJabbyMN5nE0mdz6/M6+1LHMoLmHkHnAUM9JG4fhR3B
	 Dkf49GM3/DTPmR9t/gQOFaIHbCrIHqJB7ZsWo0yNfaSjrNiT6Jvf24FAMRxg66zXfs
	 K7rd/205WzBRDUEFro4DL4sn5nWSjbPLqMhU2/Y4=
From: "kargl at gcc dot gnu.org" <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: Sat, 08 Oct 2022 16:02:06 +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: kargl at gcc dot gnu.org
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-OWnvF23W4G@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 #12 from kargl at gcc dot gnu.org ---
(In reply to Jeff Hammond from comment #11)
> > program foo
> >    use f
> >    integer i
> >    call test(i)
> > end program
> >=20
> > which specific subroutine is called based on TKR?
>=20
> I understand there is an ambiguity here, but what if I never make this ca=
ll?
> Is the module code incorrect?
>=20

21-007.pdf:C1514 is sufficiently opaque that I cannot easily decide if
a compiler needs to catch this or not.  OTOH, the TKR information is
present during compilation, it would seem appropriate that a compiler
will complain about the issue.

BTW, the original code from Chris MacMackin compiles, so at least that
portion of the PR has been fixed.=