From: "Kewen.Lin" <linkw@linux.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>,
will schmidt <will_schmidt@vnet.ibm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Bill Schmidt <wschmidt@linux.ibm.com>,
David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [PATCH] rs6000: Use rldimi for vec init instead of shift + ior
Date: Fri, 19 Feb 2021 11:06:16 +0800 [thread overview]
Message-ID: <f0e65e1f-1968-2f43-dce1-9189785eb617@linux.ibm.com> (raw)
In-Reply-To: <20210218183313.GQ28121@gate.crashing.org>
Hi Segher & Will,
Thanks for your review comments!
on 2021/2/19 上午2:33, Segher Boessenkool wrote:
> Hi!
>
> On Wed, Feb 03, 2021 at 02:37:05PM +0800, Kewen.Lin wrote:
>> This patch merges the previously approved one[1] and its relied patch
>> made by Segher here[2], it's to make unsigned int vector init go with
>> rldimi to merge two integers instead of shift and ior.
>
>> gcc/ChangeLog:
>>
>> 2020-02-03 Segher Boessenkool <segher@kernel.crashing.org>
>> Kewen Lin <linkw@gcc.gnu.org>
>>
>> * config/rs6000/rs6000.md (*rotl<mode>3_insert_3): Renamed to...
>> (rotl<mode>3_insert_3): ...this.
>> (plus_ior_xor): New code_iterator.
>> (define_split for GPR rl*imi): New splitter.
>> * config/rs6000/vsx.md (vsx_init_v4si): Use gen_rotldi3_insert_3
>> for integer merging.
>>
>> gcc/testsuite/ChangeLog:
>>
>> * gcc.target/powerpc/vec-init-10.c: New test.
>
> Is there a PR you should mention here?
I thought this is trivial so didn't file one upstream PR. I did a
searching in upstream bugzilla, PR93453 looks similar but different.
I confirmed that the current patch can't make it pass (just two insns
instead of three insns).
Do you happen to have one related in mind? If no, I will commit it
without PR.
>
>> +/* { dg-final { scan-assembler-not "sldi" } } */
>> +/* { dg-final { scan-assembler-not "or" } } */
>> +/* { dg-final { scan-assembler-times {\mrldimi\M} 4 } } */
>
> /* { dg-final { scan-assembler-not {\msldi\M} } } */
> /* { dg-final { scan-assembler-not {\mor\M} } } */
> /* { dg-final { scan-assembler-times {\mrldimi\M} 4 } } */
>
> Okay for trunk with that tweak. Thanks!
>
Will fix it, thanks!
BR,
Kewen
next prev parent reply other threads:[~2021-02-19 3:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 6:37 Kewen.Lin
2021-02-18 1:50 ` PING " Kewen.Lin
2021-02-18 17:58 ` will schmidt
2021-02-18 18:28 ` Segher Boessenkool
2021-02-18 18:33 ` Segher Boessenkool
2021-02-19 3:06 ` Kewen.Lin [this message]
2021-02-19 21:03 ` Segher Boessenkool
-- strict thread matches above, loose matches on Subject: below --
2020-12-22 8:08 Kewen.Lin
2021-01-15 0:50 ` Segher Boessenkool
2021-01-15 6:40 ` Kewen.Lin
2021-01-19 7:14 ` 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=f0e65e1f-1968-2f43-dce1-9189785eb617@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=will_schmidt@vnet.ibm.com \
--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).