From: "Kewen.Lin" <linkw@linux.ibm.com>
To: Peter Bergner <bergner@linux.ibm.com>
Cc: segher@kernel.crashing.org, dje.gcc@gmail.com,
guojiufu@linux.ibm.com, linkw@gcc.gnu.org,
gcc-patches@gcc.gnu.org, Xionghu Luo <xionghuluo@tencent.com>
Subject: Re: [PATCH v4] rs6000: Fix incorrect RTL for Power LE when removing the UNSPECS [PR106069]
Date: Wed, 19 Jun 2024 15:28:08 +0800 [thread overview]
Message-ID: <14d9c39a-2fd7-0d3b-73a5-bafdd2313be6@linux.ibm.com> (raw)
In-Reply-To: <bd5ab3f0-7d8a-42bd-9946-8a6d991266f3@linux.ibm.com>
on 2024/6/19 03:02, Peter Bergner wrote:
> On 6/12/24 2:50 AM, Kewen.Lin wrote:
>> As the recent PR115355 shows, this issue can also affect the
>> behavior when users are adopting vectorization optimization,
>> IMHO we should get this landed as soon as possible.
>
> I agree we want this fixed ASAP.
>
>
>
>
>> As all said above, I believe this patch is a correct fix and
>> considering the impact of the issue, I'd like to get this
>> pushed next week if no objections.
>
> The only complaint I have on the patch, and I know this existed before
> the patch, is we're using register_operand for the predicate for these
> patterns when we probably should be using altivec_register_operand or
> vsx_register_operand depending on the specific pattern.
Good catch.
>
> Yes, other pre-existing patterns use that, but those should probably be
> fixed too. Maybe we go with register_operand for now with this patch
> and then have a follow-on patch (from us) that cleans those all up???
Yes, since this issue existed before and sort of widely, I think we want
some other separated patch to clean them up.
>
> Otherwise, LGTM (although I can't approve it).
Thanks! I noticed Segher posted some more review comments on patch v4,
I'll follow up them. :)
BR,
Kewen
next prev parent reply other threads:[~2024-06-19 7:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 2:59 Xionghu Luo
2023-02-28 6:43 ` Ping: " Xionghu Luo
2023-03-30 19:30 ` Segher Boessenkool
2023-03-31 2:47 ` Xionghu Luo
2024-06-12 7:50 ` Kewen.Lin
2024-06-18 19:02 ` Peter Bergner
2024-06-19 7:28 ` Kewen.Lin [this message]
2024-06-18 20:31 ` Segher Boessenkool
2024-06-19 7:29 ` Kewen.Lin
-- strict thread matches above, loose matches on Subject: below --
2022-08-08 3:42 [PATCH] " Xionghu Luo
2022-08-09 3:01 ` Kewen.Lin
2022-08-10 6:39 ` [PATCH v2] " Xionghu Luo
2022-08-10 17:07 ` Segher Boessenkool
2022-08-11 6:15 ` Xionghu Luo
2022-08-16 6:53 ` Kewen.Lin
2022-08-17 6:23 ` [PATCH v4] " Xionghu Luo
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=14d9c39a-2fd7-0d3b-73a5-bafdd2313be6@linux.ibm.com \
--to=linkw@linux.ibm.com \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=guojiufu@linux.ibm.com \
--cc=linkw@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
--cc=xionghuluo@tencent.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).