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/107546] [10/11/12 Regression] simd, redundant pcmpeqb and pxor
Date: Thu, 10 Nov 2022 10:48:17 +0000 [thread overview]
Message-ID: <bug-107546-4-rNdZrp7sOq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107546-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107546
--- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:49de156a6adb50e0624479f22c20141cadef812d
commit r13-3874-g49de156a6adb50e0624479f22c20141cadef812d
Author: Jakub Jelinek <jakub@redhat.com>
Date: Thu Nov 10 11:46:52 2022 +0100
i386: Fix up ix86_expand_int_sse_cmp [PR107585]
The following patch fixes ICE on the testcase. I've used GEN_INT
incorrectly thinking the code punts on the problematic boundaries.
It does, but only for LE and GE, i.e. signed comparisons, for unsigned
the boundaries are 0 and unsigned maximum, so when say unsigned char
adds one to 127 or subtracts one from 128 we need to canonicalize it.
2022-11-10 Jakub Jelinek <jakub@redhat.com>
PR target/107585
PR target/107546
* config/i386/i386-expand.cc (ix86_expand_int_sse_cmp): Use
gen_int_mode rather than GEN_INT.
* gcc.dg/pr107585.c: New test.
next prev parent reply other threads:[~2022-11-10 10:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 6:39 [Bug rtl-optimization/107546] New: " i.nixman at autistici dot org
2022-11-07 6:51 ` [Bug target/107546] " pinskia at gcc dot gnu.org
2022-11-07 6:58 ` [Bug target/107546] [10/11/12/13 Regression] " pinskia at gcc dot gnu.org
2022-11-07 7:07 ` rguenth at gcc dot gnu.org
2022-11-07 7:07 ` crazylht at gmail dot com
2022-11-07 7:14 ` crazylht at gmail dot com
2022-11-07 7:16 ` glisse at gcc dot gnu.org
2022-11-07 7:20 ` pinskia at gcc dot gnu.org
2022-11-07 8:27 ` crazylht at gmail dot com
2022-11-07 10:22 ` jakub at gcc dot gnu.org
2022-11-07 12:02 ` jakub at gcc dot gnu.org
2022-11-07 12:05 ` i.nixman at autistici dot org
2022-11-07 13:47 ` i.nixman at autistici dot org
2022-11-08 11:24 ` cvs-commit at gcc dot gnu.org
2022-11-08 11:59 ` [Bug target/107546] [10/11/12 " jakub at gcc dot gnu.org
2022-11-10 10:48 ` cvs-commit at gcc dot gnu.org [this message]
2023-07-07 10:44 ` [Bug target/107546] [11/12 " rguenth 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-107546-4-rNdZrp7sOq@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).