From: guojiufu <guojiufu@linux.ibm.com>
To: "Kewen.Lin" <linkw@linux.ibm.com>
Cc: segher@kernel.crashing.org, dje.gcc@gmail.com, linkw@gcc.gnu.org,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] testsuite: update builtins-5-p9-runnable.c for BE
Date: Mon, 17 Apr 2023 10:42:48 +0800 [thread overview]
Message-ID: <b7ed7c3efde9bbee54443ea56f4ee86c@linux.ibm.com> (raw)
In-Reply-To: <f9796d14-af91-1c18-7452-9f3e1d4b1027@linux.ibm.com>
On 2023-04-14 17:09, Kewen.Lin wrote:
> Hi Jeff,
>
> on 2023/4/14 16:01, guojiufu wrote:
>> On 2023-04-14 15:30, Jiufu Guo wrote:
>>> Hi,
>>>
>>> As PR108809 mentioned, vec_xl_len_r and vec_xst_len_r are tested
>>> in gcc.target/powerpc/builtins-5-p9-runnable.c.
>>> The vector operand of these two bifs are different from the view
>>> of v16_int8 between BE and LE, even it is same from the view of
>>> 128bits(uint128/V1TI).
>>>
>>> The test case gcc.target/powerpc/builtins-5-p9-runnable.c was
>>> written for LE environment, this patch updates it for BE.
>>>
>>> Tested on ppc64 BE and LE.
>>> Is this ok for trunk?
>>>
>>> BR,
>>> Jeff (Jiufu)
>>>
>>> gcc/testsuite/ChangeLog:
>>>
>> PR target/108809
>
> s/target/testsuite/
>
>>> * gcc.target/powerpc/builtins-5-p9-runnable.c: Updated.
>>
>
> s/Updated/Update for BE/
>
> OK with these two nits fixed, thanks!
Thanks for the very helpful comments!
Committed via r13-7202-ga1f25e04b8d10b.
BR,
Jeff (Jiufu)
>
> BR,
> Kewen
prev parent reply other threads:[~2023-04-17 2:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 7:30 Jiufu Guo
2023-04-14 8:01 ` guojiufu
2023-04-14 9:09 ` Kewen.Lin
2023-04-17 2:42 ` guojiufu [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=b7ed7c3efde9bbee54443ea56f4ee86c@linux.ibm.com \
--to=guojiufu@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=linkw@gcc.gnu.org \
--cc=linkw@linux.ibm.com \
--cc=segher@kernel.crashing.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).