public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/104313] New: [9/10/11/12 Regression] ICE verify_gimple failed with -ff2c
Date: Mon, 31 Jan 2022 20:02:42 +0000 [thread overview]
Message-ID: <bug-104313-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104313
Bug ID: 104313
Summary: [9/10/11/12 Regression] ICE verify_gimple failed with
-ff2c
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: gscfq@t-online.de
Target Milestone: ---
Started with r9, changed between 20190728 and 20190811 :
$ cat z1.f90
function f(a)
return
end
$ gfortran-12-20220130 -c z1.f90 -ff2c
z1.f90:1:0:
1 | function f(a)
|
Error: non-trivial conversion in 'var_decl'
real(kind=8)
real(kind=4)
D.4216 = __result_f;
z1.f90:1:0: internal compiler error: 'verify_gimple' failed
0xeba38d verify_gimple_in_seq(gimple*)
../../gcc/tree-cfg.cc:5211
0xb40ea1 gimplify_body(tree_node*, bool)
../../gcc/gimplify.cc:16292
0xb41147 gimplify_function_tree(tree_node*)
../../gcc/gimplify.cc:16363
0x952b17 cgraph_node::analyze()
../../gcc/cgraphunit.cc:675
0x955dc6 analyze_functions
../../gcc/cgraphunit.cc:1240
0x956f9d symbol_table::finalize_compilation_unit()
../../gcc/cgraphunit.cc:2500
next reply other threads:[~2022-01-31 20:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 20:02 gscfq@t-online.de [this message]
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
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@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).