From: "Kewen.Lin" <linkw@linux.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
David Edelsohn <dje.gcc@gmail.com>,
Bill Schmidt <wschmidt@linux.ibm.com>
Subject: Re: [PATCH] rs6000/test: Add emulated gather test case
Date: Mon, 29 Nov 2021 10:03:43 +0800 [thread overview]
Message-ID: <0bbd3a35-2b29-1060-f1ae-8a97e25cdecb@linux.ibm.com> (raw)
In-Reply-To: <20211126162431.GQ614@gate.crashing.org>
on 2021/11/27 上午12:24, Segher Boessenkool wrote:
> Hi!
>
> On Thu, Nov 25, 2021 at 11:20:57AM +0800, Kewen.Lin wrote:
>> This patch is to add a test case similar to the one in i386
>> to add testing coverage for 510.parest_r hotspots.
>
>> gcc/testsuite/ChangeLog:
>> * gcc.target/powerpc/vect-gather-1.c: New test.
>
> This is okay for trunk. Thanks!
>
Thanks Segher! Committed as r12-5569.
BR,
Kewen
prev parent reply other threads:[~2021-11-29 2:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 3:20 Kewen.Lin
2021-11-25 5:17 ` Hongtao Liu
2021-11-25 5:31 ` Kewen.Lin
2021-11-26 16:24 ` Segher Boessenkool
2021-11-29 2:03 ` Kewen.Lin [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=0bbd3a35-2b29-1060-f1ae-8a97e25cdecb@linux.ibm.com \
--to=linkw@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
--cc=wschmidt@linux.ibm.com \
/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).