public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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 [thread overview]
Message-ID: <bug-82943-4-tdgTLDUR8y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-82943-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82943
--- 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.
> > >
> > > The problem is likely to persist for the foreseeable future
> > > as there is no one left to work on gfortran bugs. Lacking
> > > a sudden influx of new volunteer contributors, it seems
> > > the only way forward is to NOT use parameterized derived
> > > types with gfortran.
> >
> > Any news here? I seem to be having this issue with gfortran (Homebrew GCC)
> > 12.2.0
> >
> > 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 point
> > me to where I should read up on contributing?
>
> Hello!
>
> 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, and 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.
>
> 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 reading
> the documentation of the GNU Fortran rules and I hope to get the test cases
> 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 discussion.
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.
next prev parent reply other threads:[~2023-06-22 15:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-82943-4@http.gcc.gnu.org/bugzilla/>
2020-09-13 12:13 ` paul.luckner@rwth-aachen.de
2021-07-17 5:53 ` info at gha3mi dot com
2021-07-18 4:09 ` kargl at gcc dot gnu.org
2023-03-20 14:48 ` vegard.g.j at icloud dot com
2023-06-22 6:30 ` ctechnodev at gmail dot com
2023-06-22 15:43 ` kargl at gcc dot gnu.org [this message]
2023-06-24 17:21 ` ctechnodev at gmail dot com
2023-06-24 18:44 ` jvdelisle at gcc dot gnu.org
2024-01-20 18:50 ` ctechnodev at gmail dot com
2024-01-20 21:37 ` jvdelisle at gcc dot gnu.org
2024-01-20 22:35 ` sgk at troutmask dot apl.washington.edu
2024-02-29 2:15 ` cvs-commit at gcc dot gnu.org
2024-02-29 14:06 ` alexanderw at gcc dot gnu.org
2024-02-29 19:39 ` alexanderw at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-82943-4-tdgTLDUR8y@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).