public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/105624] [13 Regression] ICE in final_scan_insn_1, at final.cc:2861 (error: could not split insn)
Date: Tue, 17 May 2022 15:38:17 +0000 [thread overview]
Message-ID: <bug-105624-4-JjpRfT0Ldi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105624-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105624
--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Uros Bizjak <uros@gcc.gnu.org>:
https://gcc.gnu.org/g:61a6923e8917b6efcf349515a00a485dfd5b42e4
commit r13-563-g61a6923e8917b6efcf349515a00a485dfd5b42e4
Author: Uros Bizjak <ubizjak@gmail.com>
Date: Tue May 17 17:22:26 2022 +0200
i386: Fix ICE in final_scan_insn_1 [PR105624]
Apparently const_int_operand and other const*_operand predicates
do need constraints. Revert the offending patch that caused ICE.
2022-05-17 Uroš Bizjak <ubizjak@gmail.com>
gcc/ChangeLog:
PR target/105624
Revert:
* config/i386/i386.md: Remove constraints when used with
const_int_operand, const0_operand, const_1_operand,
constm1_operand,
const8_operand, const128_operand, const248_operand,
const123_operand,
const2367_operand, const1248_operand, const359_operand,
const_4_or_8_to_11_operand, const48_operand, const_0_to_1_operand,
const_0_to_3_operand, const_0_to_4_operand, const_0_to_5_operand,
const_0_to_7_operand, const_0_to_15_operand, const_0_to_31_operand,
const_0_to_63_operand, const_0_to_127_operand,
const_0_to_255_operand,
const_0_to_255_mul_8_operand, const_1_to_31_operand,
const_1_to_63_operand, const_2_to_3_operand, const_4_to_5_operand,
const_4_to_7_operand, const_6_to_7_operand, const_8_to_9_operand,
const_8_to_11_operand, const_8_to_15_operand,
const_10_to_11_operand,
const_12_to_13_operand, const_12_to_15_operand,
const_14_to_15_operand,
const_16_to_19_operand, const_16_to_31_operand,
const_20_to_23_operand,
const_24_to_27_operand and const_28_to_31_operand.
* config/i386/mmx.md: Ditto.
* config/i386/sse.md: Ditto.
* config/i386/subst.md: Ditto.
* config/i386/sync.md: Ditto.
gcc/testsuite/ChangeLog:
PR target/105624
* gcc.target/i386/pr105624.c: New test.
next prev parent reply other threads:[~2022-05-17 15:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 2:20 [Bug target/105624] New: " asolokha at gmx dot com
2022-05-17 6:59 ` [Bug target/105624] " rguenth at gcc dot gnu.org
2022-05-17 10:22 ` ubizjak at gmail dot com
2022-05-17 11:29 ` ubizjak at gmail dot com
2022-05-17 15:38 ` cvs-commit at gcc dot gnu.org [this message]
2022-05-17 15:41 ` ubizjak at gmail dot com
2022-05-30 12:00 ` rsandifo at gcc dot gnu.org
2022-05-30 12:21 ` ubizjak at gmail dot com
2022-05-30 12:31 ` rsandifo at gcc dot gnu.org
2022-05-30 12:49 ` ubizjak at gmail dot com
2022-05-30 19:46 ` 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-105624-4-JjpRfT0Ldi@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).