public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/99819] [9/10/11/12 Regression] ICE in gfc_defer_symbol_init, at fortran/trans-decl.c:841 Date: Fri, 27 Aug 2021 20:44:04 +0000 [thread overview] Message-ID: <bug-99819-4-xt2MJTjMJw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99819-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99819 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anlauf at gcc dot gnu.org --- Comment #5 from anlauf at gcc dot gnu.org --- Paul, are you planning to backport? This one would also (supposedly) fix pr92065.
next prev parent reply other threads:[~2021-08-27 20:44 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-29 19:35 [Bug fortran/99819] New: [9/10/11 " gscfq@t-online.de 2021-03-30 13:08 ` [Bug fortran/99819] " rguenth at gcc dot gnu.org 2021-03-30 19:43 ` anlauf at gcc dot gnu.org 2021-05-02 17:05 ` [Bug fortran/99819] [9/10/11/12 " pault at gcc dot gnu.org 2021-05-04 12:32 ` rguenth at gcc dot gnu.org 2021-05-06 13:44 ` cvs-commit at gcc dot gnu.org 2021-06-01 8:20 ` rguenth at gcc dot gnu.org 2021-08-27 20:44 ` anlauf at gcc dot gnu.org [this message] 2021-08-28 18:28 ` cvs-commit at gcc dot gnu.org 2021-08-28 18:30 ` [Bug fortran/99819] [9/10 " anlauf at gcc dot gnu.org 2021-08-30 20:13 ` cvs-commit at gcc dot gnu.org 2021-08-30 20:15 ` [Bug fortran/99819] [9 " anlauf at gcc dot gnu.org 2021-09-06 19:03 ` cvs-commit at gcc dot gnu.org 2021-09-06 19:04 ` 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-99819-4-xt2MJTjMJw@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).