public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "avieira at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/108442] New: arm: MVE's vld1* and vst1* do not work when __ARM_MVE_PRESERVE_USER_NAMESPACE is defined
Date: Wed, 18 Jan 2023 11:24:22 +0000	[thread overview]
Message-ID: <bug-108442-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 108442
           Summary: arm: MVE's vld1* and vst1* do not work when
                    __ARM_MVE_PRESERVE_USER_NAMESPACE is defined
           Product: gcc
           Version: 10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: avieira at gcc dot gnu.org
  Target Milestone: ---

When compiling:
$ cat t.c
#include <arm_mve.h>

uint32x4_t foo (uint32_t *p)
{
    return __arm_vld1q_u32 (p);
}

with:
$ arm-none-eabi-gcc -march=armv8.1-m.main+mve -mfloat-abi=hard
-D__ARM_MVE_PRESERVE_USER_NAMESPACE

it will fail to compile as __arm_vld1q_u32 is defined in arm_mve.h as calling
vldrwq_u32 which will not exist when __ARM_MVE_PRESERVE_USER_NAMESPACE is
defined.

             reply	other threads:[~2023-01-18 11:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18 11:24 avieira at gcc dot gnu.org [this message]
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

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@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).