public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109566] [13/14 Regression] powerpc: unrecognizable insn for -mcpu=e6500, -mcpu=power3, ..., -mcpu=power10
Date: Mon, 24 Apr 2023 09:50:08 +0000 [thread overview]
Message-ID: <bug-109566-4-Elf8AD8EZg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109566-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109566
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2023-04-24
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
CC| |yinyuefengyi at gmail dot com
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Ah, it ICEs on powerpc64-linux too, with -m32 -O2 -mpowerpc64 -mcpu=power3 (or
10 etc.),
-mpowerpc64 is what matters.
In *.postreload we have
(jump_insn 10 7 32 2 (parallel [
(set (pc)
(if_then_else (eq (and:DI (reg:DI 9 9 [121])
(const_int 2146435072 [0x7ff00000]))
(const_int 0 [0]))
(label_ref:SI 40)
(pc)))
(clobber (reg:DI 9 9 [125]))
(clobber (reg:CC 100 0))
]) "pr109566-3.c":6:6 229 {*branch_anddi3_dot}
(int_list:REG_BR_PROB 708669604 (nil))
The define_insn_and_split has been introduced already in GCC 12 in PR102239
r12-6433
and I'd say it is just wrong, the FAIL part doesn't belong there, that is an
ICE if for a define_insn_and_split with "#" the splitter part FAILs.
The condition on the instruction or predicates/constraints should make sure it
is splittable.
next prev parent reply other threads:[~2023-04-24 9:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 8:34 [Bug target/109566] New: powerpc: unrecognizable insn for -mcpu=e6500 sebastian.huber@embedded-brains.de
2023-04-21 8:34 ` [Bug target/109566] " sebastian.huber@embedded-brains.de
2023-04-21 8:54 ` sebastian.huber@embedded-brains.de
2023-04-24 6:31 ` [Bug target/109566] powerpc: unrecognizable insn for -mcpu=e6500, -mcpu=power3, ..., -mcpu=power10 sebastian.huber@embedded-brains.de
2023-04-24 6:33 ` sebastian.huber@embedded-brains.de
2023-04-24 8:27 ` [Bug target/109566] [13/14 Regression] " rguenth at gcc dot gnu.org
2023-04-24 8:51 ` jakub at gcc dot gnu.org
2023-04-24 9:09 ` sebastian.huber@embedded-brains.de
2023-04-24 9:32 ` jakub at gcc dot gnu.org
2023-04-24 9:50 ` jakub at gcc dot gnu.org [this message]
2023-04-24 10:09 ` jakub at gcc dot gnu.org
2023-04-24 10:33 ` jakub at gcc dot gnu.org
2023-04-24 10:37 ` jakub at gcc dot gnu.org
2023-04-24 10:54 ` [Bug target/109566] [12/13/14 " jakub at gcc dot gnu.org
2023-04-24 10:57 ` jakub at gcc dot gnu.org
2023-04-24 11:03 ` sebastian.huber@embedded-brains.de
2023-04-25 12:21 ` cvs-commit at gcc dot gnu.org
2023-04-25 12:24 ` segher at gcc dot gnu.org
2023-04-25 12:37 ` cvs-commit at gcc dot gnu.org
2023-04-25 14:12 ` [Bug target/109566] [12 " jakub at gcc dot gnu.org
2023-04-25 14:12 ` jakub at gcc dot gnu.org
2023-04-26 10:59 ` cvs-commit at gcc dot gnu.org
2023-04-26 11:00 ` 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-109566-4-Elf8AD8EZg@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).