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 tree-optimization/113677] New: Missing `VEC_PERM_EXPR <{a, CST}, CST, {0, 1, 2, ...}>` optimization
Date: Wed, 31 Jan 2024 01:46:29 +0000	[thread overview]
Message-ID: <bug-113677-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 113677
           Summary: Missing `VEC_PERM_EXPR <{a, CST}, CST, {0, 1, 2,
                    ...}>` optimization
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Keywords: missed-optimization
          Severity: enhancement
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: pinskia at gcc dot gnu.org
  Target Milestone: ---

Take:
```
#define vect32 __attribute__((vector_size(4) ))
#define vect64 __attribute__((vector_size(8) ))

vect64 unsigned char f(vect32 unsigned char a)
{
  vect32 unsigned char zero={0,0,0,0};
  return __builtin_shufflevector (a, zero, 0, 1, 2, 3, 4, 5, 6, 7);
}

```
On x86_64 this produces:
```
f:
        movd    xmm0, edi
        pxor    xmm1, xmm1
        punpckldq       xmm0, xmm1
        ret
```

We should just produce:
```
        movd    xmm0, edi
        ret
```

In .optimized we get:
```
  _1 = {a_2(D), { 0, 0, 0, 0 }};
  _3 = VEC_PERM_EXPR <_1, { 0, 0, 0, 0, 0, 0, 0, 0 }, { 0, 1, 2, 3, 8, 9, 10,
11 }>;
  return _3;
```


But _3 and _1 are the same ...

             reply	other threads:[~2024-01-31  1:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31  1:46 pinskia at gcc dot gnu.org [this message]
2024-01-31  1:47 ` [Bug tree-optimization/113677] " pinskia at gcc dot gnu.org
2024-01-31  2:16 ` pinskia at gcc dot gnu.org
2024-01-31  8:27 ` rguenth at gcc dot gnu.org
2024-02-06 17:05 ` pinskia at gcc dot gnu.org
2024-03-08  5:08 ` 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-113677-4@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).