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/99195] Optimise away vec_concat of 64-bit AdvancedSIMD operations with zeroes in aarch64
Date: Wed, 31 May 2023 16:45:10 +0000	[thread overview]
Message-ID: <bug-99195-4-c11Lwejslt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99195-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #18 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Kyrylo Tkachov <ktkachov@gcc.gnu.org>:

https://gcc.gnu.org/g:547d3bce0c02dbcbb6f62d9469a71eedf17bd688

commit r14-1447-g547d3bce0c02dbcbb6f62d9469a71eedf17bd688
Author: Kyrylo Tkachov <kyrylo.tkachov@arm.com>
Date:   Wed May 31 17:43:20 2023 +0100

    aarch64: PR target/99195 Annotate saturating mult patterns for
vec-concat-zero

    This patch goes through the various alphabet soup saturating multiplication
patterns, including those in TARGET_RDMA
    and annotates them with <vczle><vczbe>. Many other patterns are widening
and always write the full 128-bit vectors
    so this annotation doesn't apply to them. Nothing out of the ordinary in
this patch.

    Bootstrapped and tested on aarch64-none-linux and aarch64_be-none-elf.

    gcc/ChangeLog:

            PR target/99195
            * config/aarch64/aarch64-simd.md (aarch64_sq<r>dmulh<mode>): Rename
to...
            (aarch64_sq<r>dmulh<mode><vczle><vczbe>): ... This.
            (aarch64_sq<r>dmulh_n<mode>): Rename to...
            (aarch64_sq<r>dmulh_n<mode><vczle><vczbe>): ... This.
            (aarch64_sq<r>dmulh_lane<mode>): Rename to...
            (aarch64_sq<r>dmulh_lane<mode><vczle><vczbe>): ... This.
            (aarch64_sq<r>dmulh_laneq<mode>): Rename to...
            (aarch64_sq<r>dmulh_laneq<mode><vczle><vczbe>): ... This.
            (aarch64_sqrdml<SQRDMLH_AS:rdma_as>h<mode>): Rename to...
            (aarch64_sqrdml<SQRDMLH_AS:rdma_as>h<mode><vczle><vczbe>): ...
This.
            (aarch64_sqrdml<SQRDMLH_AS:rdma_as>h_lane<mode>): Rename to...
            (aarch64_sqrdml<SQRDMLH_AS:rdma_as>h_lane<mode><vczle><vczbe>): ...
This.
            (aarch64_sqrdml<SQRDMLH_AS:rdma_as>h_laneq<mode>): Rename to...
            (aarch64_sqrdml<SQRDMLH_AS:rdma_as>h_laneq<mode><vczle><vczbe>):
... This.

    gcc/testsuite/ChangeLog:

            PR target/99195
            * gcc.target/aarch64/simd/pr99195_1.c: Add tests for qdmulh,
qrdmulh.
            * gcc.target/aarch64/simd/pr99195_10.c: New test.

  parent reply	other threads:[~2023-05-31 16:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22 10:27 [Bug target/99195] New: " ktkachov at gcc dot gnu.org
2021-03-04 11:55 ` [Bug target/99195] " ktkachov at gcc dot gnu.org
2021-03-07  2:05 ` pinskia at gcc dot gnu.org
2023-04-21 17:57 ` cvs-commit at gcc dot gnu.org
2023-04-23 13:41 ` cvs-commit at gcc dot gnu.org
2023-04-25 13:55 ` cvs-commit at gcc dot gnu.org
2023-04-28  8:34 ` cvs-commit at gcc dot gnu.org
2023-05-03 10:16 ` cvs-commit at gcc dot gnu.org
2023-05-03 10:18 ` cvs-commit at gcc dot gnu.org
2023-05-04  8:45 ` cvs-commit at gcc dot gnu.org
2023-05-04  8:45 ` cvs-commit at gcc dot gnu.org
2023-05-10  9:42 ` cvs-commit at gcc dot gnu.org
2023-05-10 10:51 ` cvs-commit at gcc dot gnu.org
2023-05-10 11:02 ` cvs-commit at gcc dot gnu.org
2023-05-15  8:50 ` cvs-commit at gcc dot gnu.org
2023-05-15  8:56 ` cvs-commit at gcc dot gnu.org
2023-05-24 13:53 ` cvs-commit at gcc dot gnu.org
2023-05-25 14:01 ` cvs-commit at gcc dot gnu.org
2023-05-31 16:45 ` cvs-commit at gcc dot gnu.org [this message]
2023-05-31 16:46 ` cvs-commit at gcc dot gnu.org
2024-02-27  8:38 ` pinskia at gcc dot gnu.org
2024-04-04  8:21 ` ktkachov 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-99195-4-c11Lwejslt@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).