public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/104510] New: ICE: 'verify_gimple' failed: mismatching comparison operand types in verify_gimple_in_seq()
Date: Sat, 12 Feb 2022 06:40:55 +0000 [thread overview]
Message-ID: <bug-104510-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104510
Bug ID: 104510
Summary: ICE: 'verify_gimple' failed: mismatching comparison
operand types in verify_gimple_in_seq()
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: zsojka at seznam dot cz
Target Milestone: ---
Host: x86_64-pc-linux-gnu
Target: x86_64-pc-linux-gnu
Created attachment 52424
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52424&action=edit
reduced testcase
Compiler output:
$ x86_64-pc-linux-gnu-gcc testcase.c
testcase.c: In function 'foo':
testcase.c:5:1: error: mismatching comparison operand types
5 | foo (void)
| ^~~
_Decimal32
_Decimal64
_4 = _2 < d.1_3;
testcase.c:5:1: internal compiler error: 'verify_gimple' failed
0x13e08fd verify_gimple_in_seq(gimple*)
/repo/gcc-trunk/gcc/tree-cfg.cc:5213
0x1092686 gimplify_body(tree_node*, bool)
/repo/gcc-trunk/gcc/gimplify.cc:16302
0x10927dd gimplify_function_tree(tree_node*)
/repo/gcc-trunk/gcc/gimplify.cc:16373
0xeb6837 cgraph_node::analyze()
/repo/gcc-trunk/gcc/cgraphunit.cc:675
0xeb94a7 analyze_functions
/repo/gcc-trunk/gcc/cgraphunit.cc:1240
0xeba14d symbol_table::finalize_compilation_unit()
/repo/gcc-trunk/gcc/cgraphunit.cc:2500
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
$ x86_64-pc-linux-gnu-gcc -v
Using built-in specs.
COLLECT_GCC=/repo/gcc-trunk/binary-latest-amd64/bin/x86_64-pc-linux-gnu-gcc
COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-r12-7210-20220212001623-ge8d68f0a456-checking-yes-rtl-df-extra-nobootstrap-amd64/bin/../libexec/gcc/x86_64-pc-linux-gnu/12.0.1/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /repo/gcc-trunk//configure --enable-languages=c,c++
--enable-valgrind-annotations --disable-nls --enable-checking=yes,rtl,df,extra
--disable-bootstrap --with-cloog --with-ppl --with-isl
--build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu
--target=x86_64-pc-linux-gnu --with-ld=/usr/bin/x86_64-pc-linux-gnu-ld
--with-as=/usr/bin/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-r12-7210-20220212001623-ge8d68f0a456-checking-yes-rtl-df-extra-nobootstrap-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 12.0.1 20220212 (experimental) (GCC)
next reply other threads:[~2022-02-12 6:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 6:40 zsojka at seznam dot cz [this message]
2022-02-13 4:48 ` [Bug c/104510] " pinskia at gcc dot gnu.org
2022-02-13 4:54 ` [Bug c/104510] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org
2022-02-14 8:34 ` rguenth at gcc dot gnu.org
2022-02-14 16:33 ` jakub at gcc dot gnu.org
2022-02-14 18:14 ` jakub at gcc dot gnu.org
2022-02-16 8:26 ` cvs-commit at gcc dot gnu.org
2022-02-16 9:23 ` [Bug c/104510] [9/10/11 " jakub at gcc dot gnu.org
2022-02-19 8:03 ` cvs-commit at gcc dot gnu.org
2022-02-19 8:09 ` [Bug c/104510] [9/10 " jakub at gcc dot gnu.org
2022-05-10 8:24 ` cvs-commit at gcc dot gnu.org
2022-05-11 6:25 ` cvs-commit at gcc dot gnu.org
2022-05-11 6:36 ` jakub 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-104510-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).