public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "acoplan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/99960] MVE: Wrong code storing V2DI vector
Date: Wed, 07 Apr 2021 21:19:30 +0000 [thread overview]
Message-ID: <bug-99960-4-8foFkHSM28@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99960-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99960
--- Comment #1 from Alex Coplan <acoplan at gcc dot gnu.org> ---
Looks like both loads and stores are wrong in V2DImode:
typedef long long __attribute((vector_size(16))) v2di;
v2di load(v2di *p) { return *p; }
void store(v2di *p, v2di v) { *p = v; }
gives:
load:
vldr.64 d0, [r0]
bx lr
store:
vstr.64 d0, [r0]
bx lr
clang does:
load:
vldrw.u32 q0, [r0]
bx lr
store:
vstrw.32 q0, [r0]
bx lr
It looks like the output code for *mve_mov<mode> needs tweaking.
next prev parent reply other threads:[~2021-04-07 21:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 15:41 [Bug target/99960] New: " acoplan at gcc dot gnu.org
2021-04-07 21:19 ` acoplan at gcc dot gnu.org [this message]
2021-04-20 8:05 ` [Bug target/99960] " acoplan at gcc dot gnu.org
2021-05-10 8:47 ` cvs-commit at gcc dot gnu.org
2021-05-10 8:49 ` acoplan at gcc dot gnu.org
2021-05-24 13:58 ` cvs-commit at gcc dot gnu.org
2021-05-25 12:38 ` cvs-commit at gcc dot gnu.org
2021-05-25 12:38 ` acoplan at gcc dot gnu.org
2021-09-17 6:37 ` 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-99960-4-8foFkHSM28@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).