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/109406] Missing use of aarch64 SVE2 unpredicated integer multiply
Date: Mon, 24 Apr 2023 09:28:52 +0000	[thread overview]
Message-ID: <bug-109406-4-6L18bcKZWJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109406-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 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:9fd4a38c2f30b72ad5e3df7acb1ade201d8ac2cd

commit r14-193-g9fd4a38c2f30b72ad5e3df7acb1ade201d8ac2cd
Author: Kyrylo Tkachov <kyrylo.tkachov@arm.com>
Date:   Mon Apr 24 10:27:31 2023 +0100

    aarch64: PR target/109406 Add support for SVE2 unpredicated MUL

    SVE2 supports an unpredicated vector integer MUL form that we can emit from
our SVE expanders
    without using up a predicate registers. This patch does so.
    As the SVE MUL expansion currently is templated away through a code
iterator I did not split it
    off just for this case but instead special-cased it in the define_expand.
It seemed somewhat less
    invasive than the alternatives but I could split it off more explicitly if
others want to.
    The div-by-bitmask_1.c testcase is adjusted to expect this new MUL form.

    Bootstrapped and tested on aarch64-none-linux-gnu.

    gcc/ChangeLog:

            PR target/109406
            * config/aarch64/aarch64-sve.md (<optab><mode>3): Handle
TARGET_SVE2 MUL
            case.
            * config/aarch64/aarch64-sve2.md
(*aarch64_mul_unpredicated_<mode>): New
            pattern.

    gcc/testsuite/ChangeLog:

            PR target/109406
            * gcc.target/aarch64/sve2/div-by-bitmask_1.c: Adjust for
unpredicated SVE2
            MUL.
            * gcc.target/aarch64/sve2/unpred_mul_1.c: New test.

  parent reply	other threads:[~2023-04-24  9:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-04 14:36 [Bug target/109406] New: " ktkachov at gcc dot gnu.org
2023-04-04 14:36 ` [Bug target/109406] " ktkachov at gcc dot gnu.org
2023-04-04 18:40 ` pinskia at gcc dot gnu.org
2023-04-24  9:28 ` cvs-commit at gcc dot gnu.org [this message]
2023-04-24  9:29 ` 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-109406-4-6L18bcKZWJ@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).