From: "Kewen.Lin" <linkw@linux.ibm.com>
To: HAO CHEN GUI <guihaoc@linux.ibm.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
David <dje.gcc@gmail.com>, Peter Bergner <bergner@linux.ibm.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH-1v2, rs6000] Enable SImode in FP registers on P7 [PR88558]
Date: Wed, 27 Sep 2023 13:07:34 +0800 [thread overview]
Message-ID: <e7adbba0-0de1-a3b9-439d-8f63e4375b32@linux.ibm.com> (raw)
In-Reply-To: <7479abfd-83bc-ccff-202f-bee3168f1172@linux.ibm.com>
Hi,
on 2023/9/25 09:57, HAO CHEN GUI wrote:
> Hi Kewen,
>
> 在 2023/9/18 15:34, Kewen.Lin 写道:
>> hanks for checking! So for P7, this patch looks neutral, but for P8 and
>> later, it may cause some few differences in code gen. I'm curious that how
>> many total object files and different object files were checked and found
>> on P8?
> P8 with -O2, following object files are different.
> 507.cactuBSSN_r datestamp.o
> 511.povray_r colutils.o
> 521.wrf_r module_cu_kfeta.fppized.o
> 526.blender_r particle_edit.o
> 526.blender_r glutil.o
> 526.blender_r displist.o
> 526.blender_r CCGSubSurf.o
>
> P8 with -O3, following object files are different.
> 502.gcc_r ifcvt.o
> 502.gcc_r rtlanal.o
> 548.exchange2_r exchange2.fppized.o
> 507.cactuBSSN_r datestamp.o
> 511.povray_r colutils.o
> 521.wrf_r module_bc.fppized.o
> 521.wrf_r module_cu_kfeta.fppized.o
> 526.blender_r particle_edit.o
> 526.blender_r displist.o
> 526.blender_r CCGSubSurf.o
> 526.blender_r sketch.o
>
OK, it's concluded that the percentage of the total number of affected object
files is quite small ...
>
>
>
>> https://gcc.gnu.org/pipermail/gcc-patches/2023-February/612821.html
>> I also wonder if it's easy to reduce some of them further as small test cases.
>>
>> Since xxlor is better than fmr at least on Power10, could you also evaluate
>> the affected bmks on P10 (even P8/P9) to ensure no performance degradation?
> There is no performance recession on P10/P9/P8. The detail data is listed on
> internal issue.
... and no runtime performance impact as evaluated, so this patch looks good to
me and thanks for further testing.
Please wait for a week or so to see if Segher and David have comments. Thanks!
BR,
Kewen
>
> Thanks
> Gui Haochen
prev parent reply other threads:[~2023-09-27 5:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 5:33 HAO CHEN GUI
2023-09-12 9:33 ` Kewen.Lin
2023-09-14 8:35 ` HAO CHEN GUI
2023-09-18 7:34 ` Kewen.Lin
2023-09-25 1:57 ` HAO CHEN GUI
2023-09-27 5:07 ` 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=e7adbba0-0de1-a3b9-439d-8f63e4375b32@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=guihaoc@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).