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/96683] Arm: MVE ACLE intrinsics vst1q_{s8|u8|s16|u16} is not supported by GCC.
Date: Fri, 25 Sep 2020 08:38:56 +0000	[thread overview]
Message-ID: <bug-96683-4-H6IL1d3R98@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96683-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by SRINATH PARVATHANENI
<sripar01@gcc.gnu.org>:

https://gcc.gnu.org/g:dc0743773bef43cd3e4a8b986befa5bfebcd70f3

commit r10-8798-gdc0743773bef43cd3e4a8b986befa5bfebcd70f3
Author: Joe Ramsay <Joe.Ramsay@arm.com>
Date:   Wed Aug 19 12:34:06 2020 +0000

    arm: Require MVE memory operand for destination of vst1q intrinsic

    Previously, the machine description patterns for vst1q accepted a generic
memory
    operand for the destination, which could lead to an unrecognised builtin
when
    expanding vst1q* intrinsics. This change fixes the pattern to only accept
MVE
    memory operands.

    gcc/ChangeLog:

            PR target/96683
            * config/arm/mve.md (mve_vst1q_f<mode>): Require MVE memory operand
for
            destination.
            (mve_vst1q_<supf><mode>): Likewise.

    gcc/testsuite/ChangeLog:

            PR target/96683
            * gcc.target/arm/mve/intrinsics/vst1q_f16.c: New test.
            * gcc.target/arm/mve/intrinsics/vst1q_s16.c: New test.
            * gcc.target/arm/mve/intrinsics/vst1q_s8.c: New test.
            * gcc.target/arm/mve/intrinsics/vst1q_u16.c: New test.
            * gcc.target/arm/mve/intrinsics/vst1q_u8.c: New test.

    (cherry picked from commit 91d206adfe39ce063f6a5731b92a03c05e82e94a)

  parent reply	other threads:[~2020-09-25  8:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-18 16:55 [Bug c/96683] New: " sripar01 at gcc dot gnu.org
2020-08-18 17:03 ` [Bug c/96683] " sripar01 at gcc dot gnu.org
2020-08-20 15:27 ` cvs-commit at gcc dot gnu.org
2020-09-25  8:38 ` cvs-commit at gcc dot gnu.org [this message]
2020-10-19 12:22 ` [Bug target/96683] " sripar01 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-96683-4-H6IL1d3R98@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).