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: Mon, 18 Sep 2023 15:34:51 +0800 [thread overview]
Message-ID: <9d3194be-3799-ecf4-de6d-0339217117bf@linux.ibm.com> (raw)
In-Reply-To: <dc925d22-b8cc-41af-1e3a-deb495e21e31@linux.ibm.com>
Hi Haochen,
on 2023/9/14 16:35, HAO CHEN GUI wrote:
> Hi Kewen,
>
> 在 2023/9/12 17:33, Kewen.Lin 写道:
>> Ok, at least regression testing doesn't expose any needs to do disparaging
>> for this. Could you also test this patch with SPEC2017 for P7 and P8
>> separately at options like -O2 or -O3, to see if there is any assembly
>> change, and if yes filtering out some typical to check it's expected or
>> not? I think it can help us to better evaluate the impact. Thanks!
>
> Just compared the object files of SPEC2017 for P7 and P8. There is no
> difference between P7s'. For P8, some different object files are found.
> All differences are the same. Patched object files replace xxlor with fmr.
> It's expected as the fmr is added to ahead of xxlor in "*movsi_internal1".
Thanks 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? fmr or xxlor preference can be further considered along with existing:
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?
Thanks!
BR,
Kewen
next prev parent reply other threads:[~2023-09-18 7:35 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 [this message]
2023-09-25 1:57 ` HAO CHEN GUI
2023-09-27 5:07 ` Kewen.Lin
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=9d3194be-3799-ecf4-de6d-0339217117bf@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).