From: Segher Boessenkool <segher@kernel.crashing.org>
To: Ajit Agarwal <aagarwa1@linux.ibm.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, bergner@linux.ibm.com
Subject: Re: [PATCH v2] rs6000: fmr gets used instead of faster xxlor [PR93571]
Date: Mon, 12 Jun 2023 07:51:18 -0500 [thread overview]
Message-ID: <20230612125118.GS19790@gate.crashing.org> (raw)
In-Reply-To: <174972e2-3792-935b-ed4e-4e9d3d4ec26a@linux.ibm.com>
Hi!
On Sat, Feb 25, 2023 at 03:20:33PM +0530, Ajit Agarwal wrote:
> Here is the patch that uses xxlor instead of fmr where possible.
> Performance results shows that fmr is better in power9 and
> power10 architectures whereas xxlor is better in power7 and
> power 8 architectures. fmr is the only option before p7.
> ;; The ISA we implement.
> -(define_attr "isa" "any,p5,p6,p7,p7v,p8v,p9,p9v,p9kf,p9tf,p10"
> +(define_attr "isa" "any,p5,p6,p7,p7v,p8v,p7p8v,p9,p9v,p9kf,p9tf,p10"
> (const_string "any"))
This isn't really about what insn we *can* use here.
> + (and (eq_attr "isa" "p7p8v")
> + (match_test "TARGET_VSX && !TARGET_P9_VECTOR"))
> + (const_int 1)
What is needed here is test the *tune* setting. For example if someone
uses -mcpu=power8 -mtune=power9 (this is a setting that is really used,
or was a few years ago anyway) you *do* want fmr insns generated.
So don't do this via the isa attribute at all, just add some insn
condition (testing the tune setting)?
Segher
next prev parent reply other threads:[~2023-06-12 12:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 9:50 Ajit Agarwal
2023-06-12 8:43 ` [PING] " Ajit Agarwal
2023-06-12 12:51 ` Segher Boessenkool [this message]
2023-06-14 6:59 ` Surya Kumari Jangala
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=20230612125118.GS19790@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=aagarwa1@linux.ibm.com \
--cc=bergner@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.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).