public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle 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: Sat, 24 Jun 2023 18:44:59 +0000 [thread overview]
Message-ID: <bug-82943-4-XzoIZV7Pgg@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
Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jvdelisle at gcc dot gnu.org
--- Comment #14 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
(In reply to Alexander Westbrooks from comment #13)
> I sent in the patch to those emails. Hopefully now the ball will start
> rolling and I can slowly get this packaged into a legitimate fix. I'll post
> updates here as I receive them.
>
> The patch is below, if you would like to try it. I did this in the GCC 14
> code.
>
I saw your email. Thanks for getting involved!
next prev parent reply other threads:[~2023-06-24 18:45 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
2023-06-24 17:21 ` ctechnodev at gmail dot com
2023-06-24 18:44 ` jvdelisle at gcc dot gnu.org [this message]
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-XzoIZV7Pgg@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).