public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Kewen.Lin" <linkw@linux.ibm.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	Segher Boessenkool <segher@kernel.crashing.org>,
	Bill Schmidt <wschmidt@linux.ibm.com>,
	"Carl E. Love" <cel@us.ibm.com>
Subject: Re: [PATCH] rs6000: Use known constant for GET_MODE_NUNITS and similar
Date: Mon, 17 Jan 2022 13:48:14 +0800	[thread overview]
Message-ID: <662c2137-2851-9581-302e-6572c4b40e9c@linux.ibm.com> (raw)
In-Reply-To: <CAGWvnynbqffu3CrsFtWC5esmicU0Xv5Rc3vZDGO2L_hOk+oE0A@mail.gmail.com>

on 2022/1/14 下午9:53, David Edelsohn wrote:
> On Fri, Jan 14, 2022 at 5:42 AM Kewen.Lin <linkw@linux.ibm.com> wrote:
>>
>> on 2022/1/13 下午11:15, David Edelsohn wrote:
>>> On Thu, Jan 13, 2022 at 7:40 AM Kewen.Lin <linkw@linux.ibm.com> wrote:
>>>>
>>>> Hi David,
>>>>
>>>> on 2022/1/13 上午11:12, David Edelsohn wrote:
>>>>> On Wed, Jan 12, 2022 at 8:56 PM Kewen.Lin <linkw@linux.ibm.com> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> This patch is to clean up some codes with GET_MODE_UNIT_SIZE or
>>>>>> GET_MODE_NUNITS, which can use known constant instead.
>>>>>
>>>>> I'll let Segher decide, but often the additional code is useful
>>>>> self-documentation instead of magic constants.  Or at least the change
>>>>> requires comments documenting the derivation of the constants
>>>>> currently described by the code itself.
>>>>>
>>>>
>>>> Thanks for the comments, I added some comments as suggested, also removed
>>>> the whole "altivec_vreveti2" since I noticed it's useless, it's not used
>>>> by any built-in functions and even unused in the commit db042e1603db50573.
>>>>
>>>> The updated version has been tested as before.
>>>
>>> As we have discussed offline, the comments need to be clarified and expanded.
>>>
>>> And the removal of altivec_vreveti2 should be confirmed with Carl
>>> Love, who added the pattern less than a year ago. There may be another
>>> patch planning to use it.
>>>
>>
>> Thanks for the suggestions David!  The comments have been updated, and Carl
>> also helped to confirm the altivec_vreveti2 pattern is not planned for any
>> future work and looks reasonable to remove.
>>
>> Does this updated version look good to you?
> 
> The revised patch is okay.

Thanks!  Committed as r12-6621.

BR,
Kewen

      reply	other threads:[~2022-01-17  5:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13  1:56 Kewen.Lin
2022-01-13  3:12 ` David Edelsohn
2022-01-13 12:40   ` Kewen.Lin
2022-01-13 15:15     ` David Edelsohn
2022-01-14 10:42       ` Kewen.Lin
2022-01-14 13:53         ` David Edelsohn
2022-01-17  5:48           ` 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=662c2137-2851-9581-302e-6572c4b40e9c@linux.ibm.com \
    --to=linkw@linux.ibm.com \
    --cc=cel@us.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).