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/108442] arm: MVE's vld1* and vst1* do not work when __ARM_MVE_PRESERVE_USER_NAMESPACE is defined
Date: Thu, 18 May 2023 10:43:52 +0000	[thread overview]
Message-ID: <bug-108442-4-A7GGb4tVbg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108442-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Stam Markianos-Wright
<stammark@gcc.gnu.org>:

https://gcc.gnu.org/g:60e54b99f597a594a9ad8deaa2af1ed66eb451c7

commit r12-9611-g60e54b99f597a594a9ad8deaa2af1ed66eb451c7
Author: Murray Steele <murray.steele@arm.com>
Date:   Wed Dec 22 15:55:58 2021 +0000

    arm: fix __arm_vld1q_z* and __arm_vst1q_p* intrinsics [PR108442]

    The MVE ACLE allows for __ARM_MVE_PRESERVE_USER_NAMESPACE to be defined,
    which removes definitions for intrinsic functions without the __arm_
    prefix. __arm_vld1q_z* and __arm_vst1q_p* are currently implemented via
    calls to vldr* and vstr*, which results in several compile-time errors when
    __ARM_MVE_PRESERVE_USER_NAMESPACE is defined. This patch replaces these
    with calls to their prefixed counterparts, __arm_vldr* and __arm_str*,
    and adds a test covering the definition of
__ARM_MVE_PRESERVE_USER_NAMESPACE.

    gcc/ChangeLog:

            PR target/108442
            * config/arm/arm_mve.h (__arm_vst1q_p_u8): Use prefixed intrinsic
            function.
            (__arm_vst1q_p_s8): Likewise.
            (__arm_vld1q_z_u8): Likewise.
            (__arm_vld1q_z_s8): Likewise.
            (__arm_vst1q_p_u16): Likewise.
            (__arm_vst1q_p_s16): Likewise.
            (__arm_vld1q_z_u16): Likewise.
            (__arm_vld1q_z_s16): Likewise.
            (__arm_vst1q_p_u32): Likewise.
            (__arm_vst1q_p_s32): Likewise.
            (__arm_vld1q_z_u32): Likewise.
            (__arm_vld1q_z_s32): Likewise.
            (__arm_vld1q_z_f16): Likewise.
            (__arm_vst1q_p_f16): Likewise.
            (__arm_vld1q_z_f32): Likewise.
            (__arm_vst1q_p_f32): Likewise.

    gcc/testsuite/ChangeLog:

            * gcc.target/arm/mve/general/preserve_user_namespace_1.c: New test.

    (cherry picked from commit f54e31ddefe3ea7146624eabcb75b1c90dc59f1a)

      parent reply	other threads:[~2023-05-18 10:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18 11:24 [Bug target/108442] New: " avieira at gcc dot gnu.org
2023-01-18 11:25 ` [Bug target/108442] " avieira at gcc dot gnu.org
2023-01-18 11:26 ` rearnsha at gcc dot gnu.org
2023-01-18 11:28 ` rearnsha at gcc dot gnu.org
2023-01-18 11:59 ` cvs-commit at gcc dot gnu.org
2023-01-18 12:02 ` rearnsha at gcc dot gnu.org
2023-05-18 10:43 ` cvs-commit at gcc dot gnu.org [this message]

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-108442-4-A7GGb4tVbg@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).