public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <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 10:22:57 +0000 [thread overview]
Message-ID: <bug-105624-4-8Owkzc2fiw@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 #1 from Uroš Bizjak <ubizjak at gmail dot com> ---
Ho-hum - this was my patch that removed constraint from const_int predicates.
We are talking about:
(define_insn_and_split "*anddi_1_btr"
[(set (match_operand:DI 0 "nonimmediate_operand" "=rm")
(and:DI
(match_operand:DI 1 "nonimmediate_operand" "%0")
(match_operand:DI 2 "const_int_operand")))
(clobber (reg:CC FLAGS_REG))]
Apparently, the assumption that const_int predicates do not need cosntraints
does not hold.
next prev parent reply other threads:[~2022-05-17 10:22 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 [this message]
2022-05-17 11:29 ` ubizjak at gmail dot com
2022-05-17 15:38 ` cvs-commit at gcc dot gnu.org
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-8Owkzc2fiw@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).