public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia 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, 28 Mar 2024 23:09:28 +0000	[thread overview]
Message-ID: <bug-114514-4-JbPat6BzS2@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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement
   Last reconfirmed|                            |2024-03-28
                 CC|                            |pinskia at gcc dot gnu.org
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed.

Note non sign bit can be improved too:
```
#define vector __attribute__((vector_size(16)))

typedef vector signed char v16qi;
typedef vector unsigned char v16uqi;

v16qi
foo2 (v16qi a, v16qi b)
{
    return a >> 6;
}
v16uqi
foo1 (v16uqi a, v16uqi b)
{
    return a >> 6;
}
```

clang produces:
```
_Z4foo2Dv16_aS_:
        psrlw   $6, %xmm0
        pand    .LCPI0_0(%rip), %xmm0 #{3,3,3,...}
        movdqa  .LCPI0_1(%rip), %xmm1 #{2,2,2,...}
        pxor    %xmm1, %xmm0
        psubb   %xmm1, %xmm0
        retq
_Z4foo1Dv16_hS_:
        psrlw   $6, %xmm0
        pand    .LCPI1_0(%rip), %xmm0 #{3,3,3,...}
        retq
```

  reply	other threads:[~2024-03-28 23:09 UTC|newest]

Thread overview: 4+ 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 ` pinskia at gcc dot gnu.org [this message]
2024-03-28 23:14 ` [Bug target/114514] " pinskia at gcc dot gnu.org
2024-03-29  1:03 ` 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-JbPat6BzS2@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).