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/104313] [10/11/12/13 Regression] ICE verify_gimple failed with -ff2c since r10-2279-ge0af8f52b10385d8
Date: Fri, 15 Jul 2022 17:59:08 +0000 [thread overview]
Message-ID: <bug-104313-4-GWwXhKQeQH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104313-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104313
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |anlauf at gcc dot gnu.org
--- Comment #7 from anlauf at gcc dot gnu.org ---
(In reply to Steve Kargl from comment #6)
> The patch in comment 2 fixes the issue. It was submitted
> 13 hours after the initial report.
Steve, if you like, I can commit your patch under your name.
It's pretty obvious.
How about the following testcase?
! { dg-do compile }
! { dg-additional-options "-ff2c -fdump-tree-original" }
!
! PR fortran/104313 - ICE verify_gimple failed with -ff2c
! Contributed by G.Steinmetz
function f(a)
return
end
! { dg-final { scan-tree-dump-times "return" 1 "original" } }
next prev parent reply other threads:[~2022-07-15 17:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 20:02 [Bug fortran/104313] New: [9/10/11/12 Regression] ICE verify_gimple failed with -ff2c gscfq@t-online.de
2022-02-01 8:22 ` [Bug fortran/104313] " rguenth at gcc dot gnu.org
2022-02-01 9:09 ` [Bug fortran/104313] [9/10/11/12 Regression] ICE verify_gimple failed with -ff2c since r10-2279-ge0af8f52b10385d8 marxin at gcc dot gnu.org
2022-02-01 15:52 ` kargl at gcc dot gnu.org
2022-02-01 15:59 ` sgk at troutmask dot apl.washington.edu
2022-05-27 9:47 ` [Bug fortran/104313] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:47 ` jakub at gcc dot gnu.org
2022-06-28 15:04 ` sgk at troutmask dot apl.washington.edu
2022-07-15 17:59 ` anlauf at gcc dot gnu.org [this message]
2022-07-15 18:59 ` kargl at gcc dot gnu.org
2022-07-15 20:08 ` cvs-commit at gcc dot gnu.org
2022-07-16 18:30 ` cvs-commit at gcc dot gnu.org
2022-07-16 18:39 ` cvs-commit at gcc dot gnu.org
2022-07-16 18:48 ` cvs-commit at gcc dot gnu.org
2022-07-16 18:50 ` 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-104313-4-GWwXhKQeQH@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).