From: Michael Meissner <meissner@linux.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Michael Meissner <meissner@linux.ibm.com>,
gcc-patches@gcc.gnu.org, "Kewen.Lin" <linkw@linux.ibm.com>,
David Edelsohn <dje.gcc@gmail.com>,
Peter Bergner <bergner@linux.ibm.com>
Subject: Re: [PATCH] Fix typo in insn name.
Date: Mon, 10 Jul 2023 18:25:52 -0400 [thread overview]
Message-ID: <ZKyFcBTsLNU3ypZ7@cowardly-lion.the-meissners.org> (raw)
In-Reply-To: <20230710201021.GX19790@gate.crashing.org>
On Mon, Jul 10, 2023 at 03:10:21PM -0500, Segher Boessenkool wrote:
> Hi!
>
> On Mon, Jul 10, 2023 at 03:59:44PM -0400, Michael Meissner wrote:
> > In doing other work, I noticed that there was an insn:
> >
> > vsx_extract_v4sf_<mode>_load
> >
> > Which did not have an iterator. I removed the useless <mode>.
>
> This patch does that, you mean.
>
> > --- a/gcc/config/rs6000/vsx.md
> > +++ b/gcc/config/rs6000/vsx.md
> > @@ -3576,7 +3576,7 @@ (define_insn_and_split "vsx_extract_v4sf"
> > [(set_attr "length" "8")
> > (set_attr "type" "fp")])
> >
> > -(define_insn_and_split "*vsx_extract_v4sf_<mode>_load"
> > +(define_insn_and_split "*vsx_extract_v4sf_load"
> > [(set (match_operand:SF 0 "register_operand" "=f,v,v,?r")
> > (vec_select:SF
> > (match_operand:V4SF 1 "memory_operand" "m,Z,m,m")
>
> Does this fix any ICEs? Or do you have some example that makes better
> machine code after this change? Or would a better change perhaps be to
> just remove this pattern completely, if it doesn't do anything useful?
>
> I.e., please include a new testcase.
There is absolutely no code change. It is purely a cleanup patch. In doing
other patches, I just noticed that pattern had a _<mode> in it when it didn't
have an iterator. I just cleaned up the code removing _<mode>. I probably
should have changed it to vsx_extract_v4sf_sf_load.
--
Michael Meissner, IBM
PO Box 98, Ayer, Massachusetts, USA, 01432
email: meissner@linux.ibm.com
next prev parent reply other threads:[~2023-07-10 22:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 19:59 Michael Meissner
2023-07-10 20:10 ` Segher Boessenkool
2023-07-10 22:25 ` Michael Meissner [this message]
2023-07-24 18:44 ` Ping: " Michael Meissner
2023-07-26 5:54 ` Kewen.Lin
2023-07-26 21:53 ` Michael Meissner
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=ZKyFcBTsLNU3ypZ7@cowardly-lion.the-meissners.org \
--to=meissner@linux.ibm.com \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=linkw@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).