public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "guojiufu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/108809] gcc.target/powerpc/builtins-5-p9-runnable.c fails on power 9 BE
Date: Thu, 13 Apr 2023 09:43:07 +0000 [thread overview]
Message-ID: <bug-108809-4-MaNOIolZYr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108809-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108809
Jiu Fu Guo <guojiufu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |guojiufu at gcc dot gnu.org
--- Comment #2 from Jiu Fu Guo <guojiufu at gcc dot gnu.org> ---
(In reply to Kewen Lin from comment #1)
> It's very likely a test issue, may need to adjust some built-in function for
> endianness issue (as they have different element ordering on BE and LE).
Yeap it should be the test case issue on the difference between BE and LE:
For a buff `\001\002\003\004\005\006\a\b\t\n\v\f\r\016\017\020\021\022`,
after loading to a vector right justified, the result is different between BE
and LE.
e.g. for a vector (from 128bit view: 0x0000000000000000102030405060708),
from v16_int8 view on BE, it is v16_int8 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0,
0x0, 0x1, 0x2, 0x3, 0x4, 0x5, 0x6, 0x7, 0x8}; but from the v16_int8 view on LE,
it is v16_int8 = {0x8, 0x7, 0x6, 0x5, 0x4, 0x3, 0x2, 0x1, 0x0, 0x0, 0x0, 0x0,
0x0, 0x0, 0x0, 0x0}.
So, we would just need to update the expected result for BE for this test case.
next prev parent reply other threads:[~2023-04-13 9:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 21:57 [Bug target/108809] New: " seurer at gcc dot gnu.org
2023-03-09 7:35 ` [Bug target/108809] " linkw at gcc dot gnu.org
2023-04-13 9:43 ` guojiufu at gcc dot gnu.org [this message]
2023-04-13 12:43 ` guojiufu at gcc dot gnu.org
2023-04-17 2:39 ` [Bug testsuite/108809] " cvs-commit at gcc dot gnu.org
2023-05-09 7:37 ` guojiufu 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-108809-4-MaNOIolZYr@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).