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/112681] [14 Regression] ICE: in extract_insn, at recog.cc:2804 (unrecognizable insn) with -O2 -mfma -mno-sse4.2 and memcmp() since r14-5747
Date: Thu, 23 Nov 2023 19:59:23 +0000 [thread overview]
Message-ID: <bug-112681-4-gpQq9SRMPD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112681-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112681
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Or maybe better
--- gcc/config/i386/i386-expand.cc.jj 2023-11-21 09:31:35.792395304 +0100
+++ gcc/config/i386/i386-expand.cc 2023-11-23 20:57:57.128721762 +0100
@@ -2453,7 +2453,8 @@ ix86_expand_branch (enum rtx_code code,
/* Generate XOR since we can't check that one operand is zero
vector. */
tmp = gen_reg_rtx (mode);
- emit_insn (gen_rtx_SET (tmp, gen_rtx_XOR (mode, op0, op1)));
+ rtx ops[3] = { tmp, op0, op1 };
+ ix86_expand_vector_logical_operator (XOR, mode, ops);
tmp = gen_lowpart (p_mode, tmp);
emit_insn (gen_rtx_SET (gen_rtx_REG (CCZmode, FLAGS_REG),
gen_rtx_UNSPEC (CCZmode,
next prev parent reply other threads:[~2023-11-23 19:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 13:47 [Bug target/112681] New: [14 Regression] ICE: in extract_insn, at recog.cc:2804 (unrecognizable insn) with -O2 -mfma -mno-sse4.2 and memcmp() zsojka at seznam dot cz
2023-11-23 14:29 ` [Bug target/112681] " rguenth at gcc dot gnu.org
2023-11-23 19:04 ` [Bug target/112681] [14 Regression] ICE: in extract_insn, at recog.cc:2804 (unrecognizable insn) with -O2 -mfma -mno-sse4.2 and memcmp() since r14-5747 jakub at gcc dot gnu.org
2023-11-23 19:32 ` jakub at gcc dot gnu.org
2023-11-23 19:36 ` pinskia at gcc dot gnu.org
2023-11-23 19:46 ` jakub at gcc dot gnu.org
2023-11-23 19:59 ` jakub at gcc dot gnu.org [this message]
2023-11-23 20:04 ` jakub at gcc dot gnu.org
2023-11-23 20:28 ` manuel.lauss at googlemail dot com
2023-11-24 11:13 ` cvs-commit at gcc dot gnu.org
2023-11-24 11:13 ` 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-112681-4-gpQq9SRMPD@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).