From: guojiufu <guojiufu@linux.ibm.com>
To: Jiufu Guo <guojiufu@linux.ibm.com>
Cc: "Kewen.Lin" <linkw@linux.ibm.com>,
segher@kernel.crashing.org, dje.gcc@gmail.com, linkw@gcc.gnu.org,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 2/3]rs6000: NFC use sext_hwi to replace ((v&0xf..f)^0x80..0) - 0x80..0
Date: Thu, 01 Dec 2022 20:16:06 +0800 [thread overview]
Message-ID: <e21217a8df04cac1bc730225b273e0ce@linux.ibm.com> (raw)
In-Reply-To: <81db0995-8ba5-766c-1e0e-67d3d47c40ce@linux.ibm.com>
On 2022-12-01 15:10, Jiufu Guo via Gcc-patches wrote:
> Hi Kewen,
>
> 在 12/1/22 2:11 PM, Kewen.Lin 写道:
>> on 2022/12/1 13:35, Jiufu Guo wrote:
>>> Hi Kewen,
>>>
>>> Thanks for your quick and insight review!
>>>
>>> 在 12/1/22 1:17 PM, Kewen.Lin 写道:
>>>> Hi Jeff,
>>>>
>>>> on 2022/12/1 09:36, Jiufu Guo wrote:
>>>>> Hi,
>>>>>
>>>>> This patch just uses sext_hwi to replace the expression like:
>>>>> ((value & 0xf..f) ^ 0x80..0) - 0x80..0 for rs6000.cc and rs6000.md.
>>>>>
>>>>> Bootstrap & regtest pass on ppc64{,le}.
>>>>> Is this ok for trunk?
>>>>
>>>> You didn't say it clearly but I guessed you have grepped in the
>>>> whole
>>>> config/rs6000 directory, right? I noticed there are still two
>>>> places
>>>> using this kind of expression in function
>>>> constant_generates_xxspltiw,
>>>> but I assumed it's intentional as their types are not HOST_WIDE_INT.
>>>>
>>>> gcc/config/rs6000/rs6000.cc: short sign_h_word = ((h_word &
>>>> 0xffff) ^ 0x8000) - 0x8000;
>>>> gcc/config/rs6000/rs6000.cc: int sign_word = ((word & 0xffffffff) ^
>>>> 0x80000000) - 0x80000000;
>>>>
>>>> If so, could you state it clearly in commit log like "with type
>>>> signed/unsigned HOST_WIDE_INT" or similar?
>>>>
>>> Good question!
>>>
>>> And as you said sext_hwi is more for "signed/unsigned HOST_WIDE_INT".
>>> For these two places, it seems sext_hwi is not needed actually!
>>> And I did see why these expressions are used, may be just an
>>> assignment
>>> is ok.
>>
>> ah, I see. I agree using the assignment is quite enough. Could you
>> please also simplify them together? Since they are with the form
>> "((value & 0xf..f) ^ 0x80..0) - 0x80..0" too, and can be refactored
>> in a better way. Thanks!
>
> Sure, I believe just "short sign_h_word = vsx_const->half_words[0];"
> should be correct :-), and included in the updated patch.
>
> Updated patch is attached, bootstrap®test is on going.
Bootstrap and regtest pass on ppc64{,le}.
BR,
Jeff (Jiufu)
>
>
> BR,
> Jeff (Jiufu)
>
>>
>> BR,
>> Kewen
>>
next prev parent reply other threads:[~2022-12-01 12:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 1:36 [PATCH 1/3]rs6000: NFC use more readable pattern to clean high 32 bits Jiufu Guo
2022-12-01 1:36 ` [PATCH 2/3]rs6000: NFC use sext_hwi to replace ((v&0xf..f)^0x80..0) - 0x80..0 Jiufu Guo
2022-12-01 5:17 ` Kewen.Lin
2022-12-01 5:30 ` Kewen.Lin
2022-12-01 6:32 ` Jiufu Guo
2022-12-01 5:35 ` Jiufu Guo
2022-12-01 6:11 ` Kewen.Lin
2022-12-01 7:10 ` Jiufu Guo
2022-12-01 12:16 ` guojiufu [this message]
2022-12-02 8:56 ` Kewen.Lin
2022-12-05 6:11 ` Jiufu Guo
2022-12-09 1:51 ` Jiufu Guo
2022-12-01 1:36 ` [PATCH 3/3]rs6000: NFC no need copy_rtx in rs6000_emit_set_long_const and rs6000_emit_set_const Jiufu Guo
2022-12-01 3:31 ` Kewen.Lin
2022-12-01 4:52 ` Jiufu Guo
2022-12-09 12:25 ` Jiufu Guo
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=e21217a8df04cac1bc730225b273e0ce@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).