public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/114739] [14 Regression] ice in gfc_find_derived_types, at fortran/symbol.cc:2458
Date: Fri, 19 Apr 2024 15:45:25 +0000 [thread overview]
Message-ID: <bug-114739-4-1BZVPtOpb9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114739-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114739
--- Comment #9 from Paul Thomas <pault at gcc dot gnu.org> ---
> The incorrect errors will have to be fixed on 13-branch at very least.
> Unfortunately, this is not a question of using a backport but I will get
> onto it right away.
>
I have applied the backport manually and it works fine in eliminating the
incorrect error. I'll apply to 12- and 13-branches in a couple of weeks.
Cheers
Paul
next prev parent reply other threads:[~2024-04-19 15:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 11:10 [Bug fortran/114739] New: " dcb314 at hotmail dot com
2024-04-16 14:55 ` [Bug fortran/114739] " kargls at comcast dot net
2024-04-16 15:05 ` dcb314 at hotmail dot com
2024-04-16 16:55 ` anlauf at gcc dot gnu.org
2024-04-16 19:04 ` anlauf at gcc dot gnu.org
2024-04-16 19:27 ` anlauf at gcc dot gnu.org
2024-04-17 16:28 ` pault at gcc dot gnu.org
2024-04-18 17:07 ` cvs-commit at gcc dot gnu.org
2024-04-19 8:00 ` pault at gcc dot gnu.org
2024-04-19 15:45 ` pault at gcc dot gnu.org [this message]
2024-04-23 9:39 ` [Bug fortran/114739] Ensure no IMPLICIT type errors appear when they should for inquiry references pault at gcc dot gnu.org
2024-05-06 7:21 ` cvs-commit at gcc dot gnu.org
2024-05-06 7:45 ` cvs-commit at gcc dot gnu.org
2024-05-06 7:48 ` pault 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-114739-4-1BZVPtOpb9@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).