public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/110108] [14 Regression] Wrong code from combining VPABSB/VPBLENDVB since g:1ede03e2d0437ea9c2f7
Date: Mon, 05 Jun 2023 03:39:34 +0000 [thread overview]
Message-ID: <bug-110108-4-mhRtlz95XD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110108-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110108
--- Comment #3 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Andrew Pinski from comment #1)
> So we should be using ABSU_EXPR instead of ABS for _mm_abs_epi8 I think ...
>
> That will fix the issue.
Yes, ABSU_EXPR + VIEW_CONVERT_EXPR.
And also I notice a potential bug with -funsigned-char when folding
_mm_blendv_epi8 into VCOND_EXPR (mask < 0, a, b), -funsigned-char will always
make mask < 0 false which is not true for pblendvb, I'll submit another
separate fix to fold _mm_blendv_epi8 only without -funsigned-char
next prev parent reply other threads:[~2023-06-05 3:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-03 19:09 [Bug target/110108] New: [14 Regression] Wrong code from combining VPABSB/VPBLENDVB since 1ede03e2d0437ea9c2f7 benjsith at gmail dot com
2023-06-03 19:46 ` [Bug target/110108] [14 Regression] Wrong code from combining VPABSB/VPBLENDVB since g:1ede03e2d0437ea9c2f7 pinskia at gcc dot gnu.org
2023-06-03 19:48 ` pinskia at gcc dot gnu.org
2023-06-05 3:39 ` crazylht at gmail dot com [this message]
2023-06-05 6:48 ` rguenth at gcc dot gnu.org
2023-06-09 1:42 ` cvs-commit at gcc dot gnu.org
2023-06-09 1:42 ` cvs-commit at gcc dot gnu.org
2023-06-09 1:46 ` cvs-commit at gcc dot gnu.org
2023-06-09 1:47 ` cvs-commit at gcc dot gnu.org
2023-06-09 3:05 ` crazylht at gmail dot com
2023-06-09 11:47 ` benjsith at gmail dot com
2023-06-09 14:44 ` pinskia 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-110108-4-mhRtlz95XD@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).