public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/71703] [10/11/12/13 Regression] [OOP] ICE in wide_int_to_tree, at tree.c:1488
Date: Tue, 28 Jun 2022 10:32:24 +0000 [thread overview]
Message-ID: <bug-71703-4-8REnN8zu8D@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-71703-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71703
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|10.4 |10.5
--- Comment #19 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
GCC 10.4 is being released, retargeting bugs to GCC 10.5.
next prev parent reply other threads:[~2022-06-28 10:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-71703-4@http.gcc.gnu.org/bugzilla/>
2021-05-14 9:48 ` [Bug fortran/71703] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01 8:08 ` rguenth at gcc dot gnu.org
2021-09-30 17:10 ` cvs-commit at gcc dot gnu.org
2021-10-23 21:55 ` sandra at gcc dot gnu.org
2022-05-27 9:36 ` [Bug fortran/71703] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:32 ` jakub at gcc dot gnu.org [this message]
2023-07-07 7:30 ` [Bug fortran/71703] [11 " rguenth at gcc dot gnu.org
2024-04-23 10:07 ` 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-71703-4-8REnN8zu8D@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).