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/82199] __builtin_shuffle sometimes should produce zip1 rather than TBL
Date: Fri, 17 Jul 2020 09:20:36 +0000	[thread overview]
Message-ID: <bug-82199-4-Zm5rx4w513@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-82199-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Sandiford <rsandifo@gcc.gnu.org>:

https://gcc.gnu.org/g:7efc03fd2cb69fa0f790d32627a3e8131724e7e1

commit r11-2191-g7efc03fd2cb69fa0f790d32627a3e8131724e7e1
Author: Dmitrij Pochepko <dmitrij.pochepko@bell-sw.com>
Date:   Fri Jul 17 10:20:12 2020 +0100

    __builtin_shuffle sometimes should produce zip1 rather than TBL (PR82199)

    The following patch enables vector permutations optimization by using
    another vector element size when applicable.  It allows usage of simpler
    instructions in applicable cases.

    example:

    vector float f(vector float a, vector float b)
    {
      return __builtin_shuffle  (a, b, (vector int){0, 1, 4,5});
    }

    was compiled into:
    ...
            adrp    x0, .LC0
            ldr     q2, [x0, #:lo12:.LC0]
            tbl     v0.16b, {v0.16b - v1.16b}, v2.16b
    ...

    and after patch:
    ...
            zip1    v0.2d, v0.2d, v1.2d
    ...

    bootstrapped and tested on aarch64-linux-gnu with no regressions

    gcc/ChangeLog:

    2020-07-17  Andrew Pinski  <apinksi@marvell.com>

            PR target/82199
            * config/aarch64/aarch64.c (aarch64_evpc_reencode): New function.
            (aarch64_expand_vec_perm_const_1): Call it.

    gcc/testsuite/ChangeLog:

    2020-07-17  Andrew Pinski  <apinksi@marvell.com>

            PR target/82199
            * gcc.target/aarch64/vdup_n_3.c: New test.
            * gcc.target/aarch64/vzip_1.c: New test.
            * gcc.target/aarch64/vzip_2.c: New test.
            * gcc.target/aarch64/vzip_3.c: New test.
            * gcc.target/aarch64/vzip_4.c: New test.

    Co-Authored-By: Dmitrij Pochepko <dmitrij.pochepko@bell-sw.com>

       reply	other threads:[~2020-07-17  9:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-82199-4@http.gcc.gnu.org/bugzilla/>
2020-07-17  9:20 ` cvs-commit at gcc dot gnu.org [this message]
2020-07-21 10:03 ` rsandifo 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-82199-4-Zm5rx4w513@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).