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/99326] [10/11/12/13/14 Regression] ICE in gfc_build_dummy_array_decl, at fortran/trans-decl.c:1299 Date: Fri, 02 Jun 2023 08:28:36 +0000 [thread overview] Message-ID: <bug-99326-4-9NWnKI8uIu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99326-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99326 Paul Thomas <pault at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #7 from Paul Thomas <pault at gcc dot gnu.org> --- This bug is "auto-fixed" on trunk. I will close the PR for housekeeping purposes but will ensure that the backport of all recent associate patches do fix this bug. Thanks once more! Paul
next prev parent reply other threads:[~2023-06-02 8:28 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-01 17:09 [Bug fortran/99326] New: [9/10/11 " gscfq@t-online.de 2021-03-02 7:44 ` [Bug fortran/99326] " rguenth at gcc dot gnu.org 2021-03-02 9:53 ` marxin at gcc dot gnu.org 2021-03-02 11:39 ` burnus at gcc dot gnu.org 2021-06-01 8:19 ` [Bug fortran/99326] [9/10/11/12 " rguenth at gcc dot gnu.org 2022-05-27 9:44 ` [Bug fortran/99326] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:43 ` jakub at gcc dot gnu.org 2023-06-02 7:42 ` [Bug fortran/99326] [10/11/12/13/14 " cvs-commit at gcc dot gnu.org 2023-06-02 8:28 ` pault at gcc dot gnu.org [this message] 2023-08-27 8:51 ` cvs-commit 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-99326-4-9NWnKI8uIu@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).