public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
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] rs6000: fmr gets used instead of faster xxlor [PR93571]
Date: Tue, 21 Feb 2023 08:09:27 -0600	[thread overview]
Message-ID: <20230221140927.GQ25951@gate.crashing.org> (raw)
In-Reply-To: <46ec2582-b3a8-52c9-584a-9d282d26fb79@linux.ibm.com>

On Tue, Feb 21, 2023 at 06:00:52PM +0530, Ajit Agarwal wrote:
> On 21/02/23 4:34 pm, Segher Boessenkool wrote:
> > Please domn't use a switch, it isn't needed.  Instead use the "isa"
> > attribute (with p7v here), and put the preferred alternative first.
> 
> I am not sure how this is possible without switch and using only "isa".

You have the "p7v" "xxlor" alternative earlier than the "*" "fmr"
alternative.  You can have an "xxlor" for contraints "d", but probably
the best (and certainly the easiest) is to just move the existing
xxlor to before fmr.

Oh, the existing xxlor alternative is implicitly isa p7v, the "wa"
constraint causes that.  It may be nicer to mark it explicitly p7v as
well, nicer for the reader.

Btw, please update the other similar patterns at the same time?  There
are eight patterns with fmr in rs6000.md (the four in dfp.md should
probably not be touched); not all are similar so should be in separate
patches, if changed at all, but a bunch are completely analogous so
should not diverge.

(It is fine to first do this one pattern only, until we have worked out
all kinks, but all should be committed at the same time).

Thanks,


Segher

  reply	other threads:[~2023-02-21 14:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17 16:58 Ajit Agarwal
2023-02-17 17:09 ` Andrew Pinski
2023-02-17 17:23 ` Segher Boessenkool
2023-02-21  8:48   ` Ajit Agarwal
2023-02-21 11:04     ` Segher Boessenkool
2023-02-21 12:30       ` Ajit Agarwal
2023-02-21 14:09         ` Segher Boessenkool [this message]
2023-02-22 10:28           ` Ajit Agarwal
2023-02-24  8:11             ` Ajit Agarwal
2023-02-24 15:11               ` Segher Boessenkool
2023-02-25  7:42                 ` Ajit Agarwal

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=20230221140927.GQ25951@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).