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/104464] New: [12 Regression] ICE: in gimple_expand_vec_cond_expr, at gimple-isel.cc:268 with -O -fnon-call-exceptions -fno-tree-dce -fno-tree-forwprop -fsignaling-nans
Date: Wed, 09 Feb 2022 12:38:37 +0000 [thread overview]
Message-ID: <bug-104464-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104464
Bug ID: 104464
Summary: [12 Regression] ICE: in gimple_expand_vec_cond_expr,
at gimple-isel.cc:268 with -O -fnon-call-exceptions
-fno-tree-dce -fno-tree-forwprop -fsignaling-nans
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 52390
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52390&action=edit
reduced testcase
Compiler output:
$ x86_64-pc-linux-gnu-gcc -O -fnon-call-exceptions -fno-tree-dce
-fno-tree-forwprop -fsignaling-nans testcase.c
during GIMPLE pass: isel
testcase.c: In function 'foo':
testcase.c:5:1: internal compiler error: in gimple_expand_vec_cond_expr, at
gimple-isel.cc:268
5 | foo(void) {
| ^~~
0x7eb2b9 gimple_expand_vec_cond_expr
/repo/gcc-trunk/gcc/gimple-isel.cc:268
0x7eb2b9 gimple_expand_vec_exprs
/repo/gcc-trunk/gcc/gimple-isel.cc:297
0x7eb2b9 execute
/repo/gcc-trunk/gcc/gimple-isel.cc:351
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-7124-20220209171435-g59b31f0e2d1-checking-yes-rtl-df-extra-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
--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-7124-20220209171435-g59b31f0e2d1-checking-yes-rtl-df-extra-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 12.0.1 20220209 (experimental) (GCC)
next reply other threads:[~2022-02-09 12:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 12:38 zsojka at seznam dot cz [this message]
2022-02-09 13:42 ` [Bug tree-optimization/104464] " rguenth at gcc dot gnu.org
2022-02-09 14:50 ` cvs-commit at gcc dot gnu.org
2022-02-09 14:54 ` rguenth at gcc dot gnu.org
2023-04-17 10:44 ` 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-104464-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).