public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pheeck at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114786] New: ICE in recog.cc: unrecognizable insn while compiling bcd-3.c for power pc
Date: Sat, 20 Apr 2024 06:24:05 +0000 [thread overview]
Message-ID: <bug-114786-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114786
Bug ID: 114786
Summary: ICE in recog.cc: unrecognizable insn while compiling
bcd-3.c for power pc
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: pheeck at gcc dot gnu.org
Target Milestone: ---
Host: x86_64-linux
Target: ppc64le-linux-gnu
While compiling the GCC testsuite testcase gcc.target/powerpc/bcd-3.c with a
cross-compiler for power pc
ppc64le-linux-gnu-gcc
/home/worker/buildworker/tiber-option-juggler/build/gcc/testsuite/gcc.target/powerpc/bcd-3.c
-ffinite-math-only
the following ICE happens
/home/worker/buildworker/tiber-option-juggler/build/gcc/testsuite/gcc.target/powerpc/bcd-3.c:
In function ‘do_sub_ge’:
/home/worker/buildworker/tiber-option-juggler/build/gcc/testsuite/gcc.target/powerpc/bcd-3.c:104:1:
error: unrecognizable insn:
104 | }
| ^
(insn 22 21 23 2 (set (reg:SI 117 [ _1 ])
(ge:SI (reg:CCFP 106 6)
(const_int 0 [0])))
"/home/worker/buildworker/tiber-option-juggler/build/gcc/testsuite/gcc.target/powerpc/bcd-3.c":100:7
-1
(nil))
during RTL pass: vregs
/home/worker/buildworker/tiber-option-juggler/build/gcc/testsuite/gcc.target/powerpc/bcd-3.c:104:1:
internal compiler error: in extract_insn, at recog.cc:2812
0x656597 _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
/home/worker/buildworker/tiber-gcc-trunk-ppc64le/build/gcc/rtl-error.cc:108
0x6565b3 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
/home/worker/buildworker/tiber-gcc-trunk-ppc64le/build/gcc/rtl-error.cc:116
0x655a16 extract_insn(rtx_insn*)
/home/worker/buildworker/tiber-gcc-trunk-ppc64le/build/gcc/recog.cc:2812
0x92d390 instantiate_virtual_regs_in_insn
/home/worker/buildworker/tiber-gcc-trunk-ppc64le/build/gcc/function.cc:1612
0x92d390 instantiate_virtual_regs
/home/worker/buildworker/tiber-gcc-trunk-ppc64le/build/gcc/function.cc:1995
0x92d390 execute
/home/worker/buildworker/tiber-gcc-trunk-ppc64le/build/gcc/function.cc:2042
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.
ppc64le-linux-gnu-gcc -v
Using built-in specs.
COLLECT_GCC=/home/worker/cross/bin/ppc64le-linux-gnu-gcc
COLLECT_LTO_WRAPPER=/home/worker/cross/libexec/gcc/ppc64le-linux-gnu/14.0.1/lto-wrapper
Target: ppc64le-linux-gnu
Configured with:
/home/worker/buildworker/tiber-gcc-trunk-ppc64le/build/configure
--enable-languages=c,c++,fortran --disable-bootstrap --disable-libsanitizer
--disable-multilib --enable-checking=release --prefix=/home/worker/cross
--target=ppc64le-linux-gnu --with-as=/usr/bin/powerpc64le-suse-linux-as
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.0.1 20240419 (experimental)
c23db3ebb65ba357155be85ef56d037403eaee36 (GCC)
next reply other threads:[~2024-04-20 6:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-20 6:24 pheeck at gcc dot gnu.org [this message]
2024-04-23 5:37 ` [Bug target/114786] " guojiufu 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-114786-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).