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/103366] [10/11/12/13/14 Regression] ICE in gfc_conv_gfc_desc_to_cfi_desc, at fortran/trans-expr.c:5647
Date: Wed, 19 Apr 2023 09:19:44 +0000 [thread overview]
Message-ID: <bug-103366-4-IoEeXPGaOD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103366-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103366
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |FIXED
Target Milestone|10.5 |12.3
--- Comment #12 from Paul Thomas <pault at gcc dot gnu.org> ---
(In reply to anlauf from comment #11)
> (In reply to CVS Commits from comment #8)
> > The master branch has been updated by Paul Thomas <pault@gcc.gnu.org>:
> >
> > https://gcc.gnu.org/g:828474fafd2ed33430172fe227f9da7d6fb98723
> >
> > commit r12-6419-g828474fafd2ed33430172fe227f9da7d6fb98723
>
> This patch is installed for 12-branch and 13-trunk. The surrounding code
> was added during 12 development, so a backport would not be possible.
>
> Can we mark this fixed for 12/13?
>
> Does it still occur in 10/11?
>
> Should we set the target milestone to 12.2 and close this PR?
It still occurs in 10-/11-branches. However, as you say, a backport will be
"slightly impossible".
Closing as fixed.
Paul
prev parent reply other threads:[~2023-04-19 9:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 19:38 [Bug fortran/103366] New: [12 " gscfq@t-online.de
2021-11-23 7:33 ` [Bug fortran/103366] " rguenth at gcc dot gnu.org
2021-11-23 7:56 ` marxin at gcc dot gnu.org
2021-11-23 8:01 ` pinskia at gcc dot gnu.org
2021-11-23 8:10 ` marxin at gcc dot gnu.org
2021-11-23 8:12 ` [Bug fortran/103366] [9/10/11/12 " pinskia at gcc dot gnu.org
2022-01-03 9:15 ` pault at gcc dot gnu.org
2022-01-03 11:55 ` pault at gcc dot gnu.org
2022-01-03 12:33 ` pault at gcc dot gnu.org
2022-01-06 1:07 ` sandra at gcc dot gnu.org
2022-01-10 16:55 ` cvs-commit at gcc dot gnu.org
2022-05-27 9:46 ` [Bug fortran/103366] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:47 ` jakub at gcc dot gnu.org
2022-07-13 19:16 ` anlauf at gcc dot gnu.org
2023-04-19 9:19 ` pault at gcc dot gnu.org [this message]
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-103366-4-IoEeXPGaOD@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).