From: "Kewen.Lin" <linkw@linux.ibm.com>
To: Carl Love <cel@linux.ibm.com>
Cc: gcc-patches@gcc.gnu.org,
Segher Boessenkool <segher@kernel.crashing.org>,
"bergner@linux.ibm.com" <bergner@linux.ibm.com>
Subject: Re: [PATCH 1/13 ver 3] rs6000, Remove __builtin_vsx_cmple* builtins
Date: Thu, 6 Jun 2024 10:40:31 +0800 [thread overview]
Message-ID: <096b61ba-689f-2ffd-be4c-cdf462d50d31@linux.ibm.com> (raw)
In-Reply-To: <8e290bb2-7174-4150-a43d-5e0adfeb6891@linux.ibm.com>
Hi Carl,
on 2024/6/6 06:25, Carl Love wrote:
> Kewen:
>
> On 6/3/24 23:00, Kewen.Lin wrote:
>> Hi Carl,
>>
>> on 2024/5/29 23:52, Carl Love wrote:
>>> This patch was approved in the previous series. There are no changes to this patch. Reposting for completeness.
>> I guess you can just push the approved ones, as there is no dependency
>> between any two of them? It can help to reduce the size of this series.
>
> The patches do touch some similar files so they are not completely independent from a patch standpoint. Functionally they are all independent.
>
> I tried applying the approved patches only to the current mainline tree. The approved patches were: 1,3,5 (with tweak), 6, 8, 9, 10, 12. Patch 5 requires a little rebasing due to a little fuzz in the lines. Not a big deal. Patch 8 also doesn't apply cleanly with git. The patch command gets a little confused when I tried to use it, so I had to manually "recreate" the patch. The changes are straight forward so that is fairly easy. The rest of the patches applied cleanly with git. I am guessing there will be some rebasing needed for the non-approved patches to apply them after the approved patches.
IMHO, you can first reorder the patches in your WIP branch (like the approved ones go first) with git rebase -i,
then rebase with the latest trunk, there may be some conflicts but I'd expect there are not many.
>
> The main reason that I reposted everything was that the patch numbers changed and I wanted it to be fairly clear what was going on.
OK, if you push them, you can also specify the commit hashes for the pushed ones in cover letter.
>
> I toyed with the idea of committing the 8 approved patches and then working on the additional 5 but I think that is hard as I would have to manually adjust the patch numbers to keep them lined up with version 3 or version 4 has a new numbering patches 1 to 5 (i.e. remapping of version 3 patch numbers). Either way I think it would be hard/confusing.
>
> Given that separating out the approved and non-approved patches causes some re-basing issues, it is probably best to just update the 5 patches, posting them as version 4 and not re-post the whole series. I will just note in the header patch 0/13 the patches that have already been approved. I hope that is ok?
Sure, I'm totally fine if you prefer this way. :)
BR,
Kewen
next prev parent reply other threads:[~2024-06-06 2:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 15:48 [PATCH 0/13 ver 3] rs6000, built-in cleanup patch series Carl Love
2024-05-29 15:52 ` [PATCH 1/13 ver 3] s6000, Remove __builtin_vsx_cmple* builtins Carl Love
2024-06-04 6:00 ` [PATCH 1/13 ver 3] rs6000, " Kewen.Lin
2024-06-05 22:25 ` Carl Love
2024-06-06 2:40 ` Kewen.Lin [this message]
2024-05-29 15:55 ` [PATCH 2/13 ver 3] rs6000, Remove __builtin_vsx_xvcvspsxws built-in Carl Love
2024-05-29 15:56 ` [PATCH 3/13 ver 3] rs6000, fix error in unsigned vector float to unsigned int built-in definition Carl Love
2024-06-04 5:58 ` Kewen.Lin
2024-05-29 15:58 ` [PATCH 4/13 ver 3] rs6000, extend the current vec_{un,}signed{e,o} built-ins Carl Love
2024-06-04 7:19 ` Kewen.Lin
2024-06-13 15:35 ` Carl Love
2024-05-29 16:00 ` [PATCH 5/13 ver 3] rs6000, Remove redundant float/double type conversions Carl Love
2024-06-04 6:20 ` Kewen.Lin
2024-05-29 16:01 ` [PATCH 6/13 ver 3] rs6000, remove duplicated built-ins of vecmergl and, vec_mergeh Carl Love
2024-05-29 16:03 ` [PATCH 7/13 ver 3] rs6000, add overloaded vec_sel with int128 arguments Carl Love
2024-06-04 5:58 ` Kewen.Lin
2024-06-13 15:35 ` Carl Love
2024-05-29 16:05 ` [PATCH 8/13 ver 3] rs6000, remove the vec_xxsel built-ins, they are, duplicates Carl Love
2024-06-04 5:58 ` Kewen.Lin
2024-05-29 16:06 ` [PATCH 9/13 ver 3] rs6000, remove __builtin_vsx_vperm_* built-ins Carl Love
2024-06-04 5:58 ` Kewen.Lin
2024-05-29 16:08 ` [PATCH 10/13 ver 3] rs6000, remove __builtin_vsx_xvnegdp and, __builtin_vsx_xvnegsp built-ins Carl Love
2024-05-29 16:10 ` [PATCH 11/13 ver 3] rs6000, extend vec_xxpermdi built-in for __int128 args Carl Love
2024-06-04 5:58 ` Kewen.Lin
2024-06-13 15:35 ` Carl Love
2024-05-29 16:11 ` [PATCH 12/13 ver 3] rs6000, remove __builtin_vsx_xvcmpeqsp_p built-in Carl Love
2024-06-04 5:59 ` Kewen.Lin
2024-05-29 16:16 ` [PATCH 13/13 ver 3] rs6000, remove vector set and vector init built-ins Carl Love
2024-06-04 5:59 ` Kewen.Lin
2024-06-13 15:35 ` Carl Love
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=096b61ba-689f-2ffd-be4c-cdf462d50d31@linux.ibm.com \
--to=linkw@linux.ibm.com \
--cc=bergner@linux.ibm.com \
--cc=cel@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--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).