public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/115466] rs6000 vec_ld built-in works on BE but not LE
Date: Wed, 12 Jun 2024 21:25:44 +0000 [thread overview]
Message-ID: <bug-115466-4-Anf3je4wMQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115466-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115466
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2024-06-12
Status|UNCONFIRMED |WAITING
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
> int ia[8] = {1, 2, 3, 4, 5, 6, 7, 8};
> float fa[8] = {10.0, 20.0, 30.0, 40.0, 50.0, 60.0, 70.0, 80.0};
The way vec_ld works is is (a+b)&~0xf is the address which is being loaded.
Both ia and fa are not specified as being aligned to the 16byte boundary so it
could be loading from before hand.
What happens if you do:
int ia[8] __attribute__((aligned(16))) = {1, 2, 3, 4, 5, 6, 7, 8};
float fa[8] __attribute__((aligned(16))) = {10.0, 20.0, 30.0, 40.0, 50.0,
60.0, 70.0, 80.0};
Instead?
next prev parent reply other threads:[~2024-06-12 21:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 21:13 [Bug target/115466] New: " carll at gcc dot gnu.org
2024-06-12 21:25 ` pinskia at gcc dot gnu.org [this message]
2024-06-13 8:10 ` [Bug target/115466] " linkw at gcc dot gnu.org
2024-06-13 13:56 ` segher at gcc dot gnu.org
2024-06-13 15:27 ` carll at gcc dot gnu.org
2024-06-13 18:36 ` segher at gcc dot gnu.org
2024-06-13 18:44 ` carll at gcc dot gnu.org
2024-07-03 3:31 ` linkw 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-115466-4-Anf3je4wMQ@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).