public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/100273] [11/12/13/14 Regression] ICE in gfc_create_module_variable, at fortran/trans-decl.c:5352 Date: Fri, 07 Jul 2023 10:39:39 +0000 [thread overview] Message-ID: <bug-100273-4-PrW4c1uNo4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100273-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100273 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|10.5 |11.5 --- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> --- GCC 10 branch is being closed.
next prev parent reply other threads:[~2023-07-07 10:39 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-26 19:43 [Bug fortran/100273] New: [9/10/11/12 " gscfq@t-online.de 2021-04-26 19:44 ` [Bug fortran/100273] " gscfq@t-online.de 2021-04-26 20:52 ` anlauf at gcc dot gnu.org 2021-04-26 20:52 ` anlauf at gcc dot gnu.org 2021-06-01 8:20 ` rguenth at gcc dot gnu.org 2022-05-27 9:45 ` [Bug fortran/100273] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:44 ` jakub at gcc dot gnu.org 2023-07-07 10:39 ` rguenth at gcc dot gnu.org [this message] 2024-07-16 18:29 ` [Bug fortran/100273] [11/12/13/14/15 " anlauf at gcc dot gnu.org 2024-07-19 13:11 ` [Bug fortran/100273] [12/13/14/15 " rguenth at gcc dot gnu.org 2024-09-04 19:40 ` anlauf at gcc dot gnu.org 2024-09-05 19:44 ` anlauf at gcc dot gnu.org 2024-09-05 19:59 ` cvs-commit at gcc dot gnu.org 2024-09-05 20:02 ` [Bug fortran/100273] [12/13/14 " anlauf at gcc dot gnu.org 2024-09-20 19:35 ` cvs-commit at gcc dot gnu.org 2024-09-20 20:25 ` cvs-commit at gcc dot gnu.org 2024-09-20 20:28 ` cvs-commit at gcc dot gnu.org 2024-09-20 20:30 ` anlauf 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-100273-4-PrW4c1uNo4@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: linkBe 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).