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/113869] V4HF->V4SF pattern seems to be missing
Date: Thu, 06 Jun 2024 18:51:00 +0000	[thread overview]
Message-ID: <bug-113869-4-6Qy1dxrvQe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113869-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Pengxuan Zheng <pzheng@gcc.gnu.org>:

https://gcc.gnu.org/g:230d62a2cdd16c1ec8fe87998ec01081503f010d

commit r15-1079-g230d62a2cdd16c1ec8fe87998ec01081503f010d
Author: Pengxuan Zheng <quic_pzheng@quicinc.com>
Date:   Thu May 30 17:53:23 2024 -0700

    aarch64: Add vector floating point extend pattern [PR113880, PR113869]

    This patch adds vector floating point extend pattern for V2SF->V2DF and
    V4HF->V4SF conversions by renaming the existing
aarch64_float_extend_lo_<Vwide>
    pattern to the standard optab one, i.e., extend<mode><Vwide>2. This allows
the
    vectorizer to vectorize certain floating point widening operations for the
    aarch64 target.

            PR target/113880
            PR target/113869

    gcc/ChangeLog:

            * config/aarch64/aarch64-builtins.cc (VAR1): Remap float_extend_lo_
            builtin codes to standard optab ones.
            * config/aarch64/aarch64-simd.md (aarch64_float_extend_lo_<Vwide>):
Rename
            to...
            (extend<mode><Vwide>2): ... This.

    gcc/testsuite/ChangeLog:

            * gcc.target/aarch64/extend-vec.c: New test.

    Signed-off-by: Pengxuan Zheng <quic_pzheng@quicinc.com>

  reply	other threads:[~2024-06-06 18:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-11  1:31 [Bug target/113869] New: " pinskia at gcc dot gnu.org
2024-06-06 18:51 ` cvs-commit at gcc dot gnu.org [this message]
2024-06-11 17:03 ` [Bug target/113869] " 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-113869-4-6Qy1dxrvQe@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).