public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/96041] [11 regression] ICE in gfortran.dg/pr93423.f90 after r11-1792 Date: Thu, 17 Sep 2020 12:07:13 +0000 [thread overview] Message-ID: <bug-96041-4-RYWrMpGsal@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96041-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96041 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #11 from Tobias Burnus <burnus at gcc dot gnu.org> --- FIXED on trunk (GCC 11), which is the only one affected. Note: The patch causing this issue is for PR93423. The latter was a 8/9/10/11 regression of type ICE-on-invalid. If the PR93423 patch gets cherry-picked for a branch, you may likely also see cherry-picks commits in PR.
next prev parent reply other threads:[~2020-09-17 12:07 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-02 22:45 [Bug fortran/96041] New: " seurer at linux dot vnet.ibm.com 2020-07-03 6:59 ` [Bug fortran/96041] " rguenth at gcc dot gnu.org 2020-07-03 18:27 ` anlauf at gcc dot gnu.org 2020-07-04 5:59 ` dominiq at lps dot ens.fr 2020-07-04 14:29 ` dominiq at lps dot ens.fr 2020-07-04 17:17 ` anlauf at gcc dot gnu.org 2020-07-06 14:35 ` seurer at linux dot vnet.ibm.com 2020-07-06 18:26 ` anlauf at gcc dot gnu.org 2020-07-07 12:03 ` dominiq at lps dot ens.fr 2020-07-07 19:31 ` anlauf at gcc dot gnu.org 2020-09-14 22:52 ` burnus at gcc dot gnu.org 2020-09-17 12:01 ` cvs-commit at gcc dot gnu.org 2020-09-17 12:07 ` burnus at gcc dot gnu.org [this message] 2020-09-18 20:19 ` cvs-commit at gcc dot gnu.org 2020-09-19 18:32 ` cvs-commit at gcc dot gnu.org 2020-09-19 18:42 ` 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-96041-4-RYWrMpGsal@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).