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/114514] v16qi >> 7 can be optimized with vpcmpgtb
Date: Thu, 16 May 2024 00:41:14 +0000	[thread overview]
Message-ID: <bug-114514-4-oWHNG2uUau@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114514-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114514

--- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by hongtao Liu <liuhongt@gcc.gnu.org>:

https://gcc.gnu.org/g:0cc0956b3bb8bcbc9196075b9073a227d799e042

commit r15-529-g0cc0956b3bb8bcbc9196075b9073a227d799e042
Author: liuhongt <hongtao.liu@intel.com>
Date:   Tue May 14 18:39:54 2024 +0800

    Optimize ashift >> 7 to vpcmpgtb for vector int8.

    Since there is no corresponding instruction, the shift operation for
    vector int8 is implemented using the instructions for vector int16,
    but for some special shift counts, it can be transformed into vpcmpgtb.

    gcc/ChangeLog:

            PR target/114514
            * config/i386/i386-expand.cc
            (ix86_expand_vec_shift_qihi_constant): Optimize ashift >> 7 to
            vpcmpgtb.
            (ix86_expand_vecop_qihi_partial): Ditto.

    gcc/testsuite/ChangeLog:

            * gcc.target/i386/pr114514-shift.c: New test.

  parent reply	other threads:[~2024-05-16  0:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28  9:38 [Bug target/114514] New: " liuhongt at gcc dot gnu.org
2024-03-28 23:09 ` [Bug target/114514] " pinskia at gcc dot gnu.org
2024-03-28 23:14 ` pinskia at gcc dot gnu.org
2024-03-29  1:03 ` liuhongt at gcc dot gnu.org
2024-05-16  0:41 ` cvs-commit at gcc dot gnu.org [this message]
2024-05-16  0:41 ` cvs-commit at gcc dot gnu.org
2024-05-16  0:42 ` liuhongt 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-114514-4-oWHNG2uUau@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).