public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Kewen.Lin" <linkw@linux.ibm.com>
To: gcc-patches@gcc.gnu.org
Cc: Bill Schmidt <wschmidt@linux.ibm.com>,
	David Edelsohn <dje.gcc@gmail.com>,
	Segher Boessenkool <segher@kernel.crashing.org>
Subject: PING^2 [PATCH v2] rs6000: Use direct move for char/short vector CTOR [PR96933]
Date: Mon, 2 Nov 2020 17:11:10 +0800	[thread overview]
Message-ID: <dd449fc2-5d03-020c-6c59-30af6e86518f@linux.ibm.com> (raw)
In-Reply-To: <f33eafb6-24c4-a8a5-b33e-fd78bc32ee9b@linux.ibm.com>

Hi,

Gentle ping for the patch:
  
https://gcc.gnu.org/pipermail/gcc-patches/2020-September/553555.html

BR,
Kewen

on 2020/10/13 下午2:59, Kewen.Lin via Gcc-patches wrote:
> Hi,
> 
> I'd like to gentle ping this patch:
> 
> https://gcc.gnu.org/pipermail/gcc-patches/2020-September/553555.html
> 
> BR,
> Kewen
> 
> on 2020/9/10 上午11:19, Kewen.Lin via Gcc-patches wrote:
>> Hi,
>>
>> As Segher's suggestion in the PR, for 128bit_direct_move, this new
>> version leverages vector pack insns instead of vector perms with
>> one control vector.  The performance evaluation shows that it's on
>> par with the previous version for char, while it's better than the
>> previous for short.
>>
>> Bootstrapped/regtested again on powerpc64{,le}-linux-gnu P8 and
>> powerpc64le-linux-gnu P9.
>>
>> Is it ok for trunk?
>>
>> BR,
>> Kewen
>> ------------
>>
>> gcc/ChangeLog:
>>
>> 	PR target/96933
>> 	* config/rs6000/rs6000.c (rs6000_expand_vector_init): Use direct move
>> 	instructions for vector construction with char/short types.
>> 	* config/rs6000/rs6000.md (p8_mtvsrwz_v16qisi2): New define_insn.
>> 	(p8_mtvsrd_v16qidi2): Likewise. 
>>
>> gcc/testsuite/ChangeLog:
>>
>> 	PR target/96933
>> 	* gcc.target/powerpc/pr96933-1.c: New test.
>> 	* gcc.target/powerpc/pr96933-2.c: New test.
>> 	* gcc.target/powerpc/pr96933-3.c: New test.
>> 	* gcc.target/powerpc/pr96933.h: New test.
>>

  reply	other threads:[~2020-11-02  9:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-08  7:55 [PATCH] " Kewen.Lin
2020-09-10  3:19 ` [PATCH v2] " Kewen.Lin
2020-10-13  6:59   ` PING^1 " Kewen.Lin
2020-11-02  9:11     ` Kewen.Lin [this message]
2020-11-02 13:44       ` PING^2 " David Edelsohn
2020-11-03  7:25         ` [PATCH v3] " Kewen.Lin
2020-11-03 16:45           ` Segher Boessenkool
2020-11-05  8:27             ` Kewen.Lin

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=dd449fc2-5d03-020c-6c59-30af6e86518f@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).