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/110108] [14 Regression] Wrong code from combining VPABSB/VPBLENDVB since g:1ede03e2d0437ea9c2f7
Date: Fri, 09 Jun 2023 01:47:08 +0000	[thread overview]
Message-ID: <bug-110108-4-61wxz250m3@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 #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by hongtao Liu
<liuhongt@gcc.gnu.org>:

https://gcc.gnu.org/g:887f903ab05ddcac498247384734efbc6cf45147

commit r12-9686-g887f903ab05ddcac498247384734efbc6cf45147
Author: liuhongt <hongtao.liu@intel.com>
Date:   Mon Jun 5 12:38:41 2023 +0800

    Explicitly view_convert_expr mask to signed type when folding pblendvb
builtins.

    Since mask < 0 will be always false for vector char when
    -funsigned-char, but vpblendvb needs to check the most significant
    bit. The patch explicitly VCE to vector signed char.

    gcc/ChangeLog:

            PR target/110108
            * config/i386/i386.cc (ix86_gimple_fold_builtin): Explicitly
            view_convert_expr mask to signed type when folding pblendvb
            builtins.

    gcc/testsuite/ChangeLog:

            * gcc.target/i386/pr110108-2.c: New test.

  parent reply	other threads:[~2023-06-09  1:47 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
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 [this message]
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-61wxz250m3@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).