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 7538F3858C5E; Thu, 22 Jun 2023 15:43:42 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7538F3858C5E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1687448622;
	bh=j8UkY2QR0dGZsGbbE6nKwx8KCBt289PMIjKzP1bY4GE=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=khmwcCWMf5Hc6sp6AiA3BTBDLAbtiQb7AzKt2cQI7KgFsntk0mGDivNCruFPb1qvI
	 WsHetIvdBPVxghDTSGz9Xyw1p3uQwbSSeqS70idPZesmiWUDvahoB3WvrDqj98Ue1G
	 wHG4vtMlD1VhhyySNc0auXycLzqjHvcW/A5zk5qk=
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82943] [F03] Error with type-bound procedure of
 parametrized derived type
Date: Thu, 22 Jun 2023 15:43:41 +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: 8.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
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-82943-4-tdgTLDUR8y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82943-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82943-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=3D82943

--- Comment #12 from kargl at gcc dot gnu.org ---
(In reply to Alexander Westbrooks from comment #11)
> (In reply to vegard from comment #10)
> > (In reply to kargl from comment #9)
> > > (In reply to alig from comment #8)
> > > > The problem still persists with GNU Fortran (GCC) 11.1.0.
> > >=20
> > > The problem is likely to persist for the foreseeable future
> > > as there is no one left to work on gfortran bugs.  Lacking=20
> > > a sudden influx of new volunteer contributors, it seems
> > > the only way forward is to NOT use parameterized derived=20
> > > types with gfortran.
> >=20
> > Any news here? I seem to be having this issue with gfortran (Homebrew G=
CC)
> > 12.2.0
> >=20
> > As a side note: I'm somewhat new to the fortran community, but could see
> > myself contributing to gfortran in the future. Do you think you could p=
oint
> > me to where I should read up on contributing?
>=20
> Hello!
>=20
> I'm new to the community as well. I have had the same issue with this bug
> and first encountered it 5 years ago while working on my thesis. Two weeks
> ago I decided to tackle this bug. I have found the issues in the code, an=
d I
> was able to successfully compiles the following example. I made sure that
> the LEN type parameter condition was enforced as janus@gcc.gnu.org stated=
 in
> Comment #6 and I used inheritance in this example to test the added logic=
 to
> ensure that a PDT instance belonged to a PDT template.=20
>=20
> The only things I have left to do is write applicable test cases (which I
> haven't done before. I am learning how to use the DejaGNU framework as I
> work on this) and obtain some guidance on how to get this code verified by
> others and ultimately accepted as fixed code into the compiler. I am read=
ing
> the documentation of the GNU Fortran rules and I hope to get the test cas=
es
> completed and have the fix under review within the next couple of weeks.

Your contribution will likely be most welcomed.  I encourage you to send the
patch to fortran@gcc.gnu.org and gcc-patches@gcc.gnu.org to open up discuss=
ion.
For testcases, look in gcc/testsuite/gfortran.dg for files with the string
'pdt' in the name.  Copy one of those and adjust it to suit your needs.=