From: will schmidt <will_schmidt@vnet.ibm.com>
To: Michael Meissner <meissner@linux.ibm.com>,
gcc-patches@gcc.gnu.org,
Segher Boessenkool <segher@kernel.crashing.org>,
David Edelsohn <dje.gcc@gmail.com>,
Bill Schmidt <wschmidt@linux.ibm.com>,
Peter Bergner <bergner@linux.ibm.com>
Subject: Re: [PATCH 2/2] Fix xxeval predicates.
Date: Thu, 20 May 2021 14:31:08 -0500 [thread overview]
Message-ID: <78c90b0ca123aeb85bfb60ff7c9a69180755049b.camel@vnet.ibm.com> (raw)
In-Reply-To: <20210518204758.GB16671@ibm-toto.the-meissners.org>
On Tue, 2021-05-18 at 16:47 -0400, Michael Meissner wrote:
> [PATCH 2/2] Fix xxeval predicates.
>
> In doing the patch to move the XX* built-in functions from altivec.md to
> vsx.md, I noticed that the xxeval built-in function used the
> altivec_register_operand predicate. Since it takes vsx registers, this
> might force the register allocate to issue a move when it could use a
> traditional floating point register. This patch fixes that.
allocator ?
>
> gcc/
> 2021-05-18 Michael Meissner <meissner@linux.ibm.com>
>
> * config/rs6000/vsx.md (xxeval): Use register_predicate instead of
> altivec_register_predicate.
> ---
> gcc/config/rs6000/vsx.md | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/gcc/config/rs6000/vsx.md b/gcc/config/rs6000/vsx.md
> index a859038d399..15a8c0e22d8 100644
> --- a/gcc/config/rs6000/vsx.md
> +++ b/gcc/config/rs6000/vsx.md
> @@ -6410,9 +6410,9 @@ (define_insn "xxpermx_inst"
> ;; XXEVAL built-in function support
> (define_insn "xxeval"
> [(set (match_operand:V2DI 0 "register_operand" "=wa")
> - (unspec:V2DI [(match_operand:V2DI 1 "altivec_register_operand" "wa")
> - (match_operand:V2DI 2 "altivec_register_operand" "wa")
> - (match_operand:V2DI 3 "altivec_register_operand" "wa")
> + (unspec:V2DI [(match_operand:V2DI 1 "register_operand" "wa")
> + (match_operand:V2DI 2 "register_operand" "wa")
> + (match_operand:V2DI 3 "register_operand" "wa")
> (match_operand:QI 4 "u8bit_cint_operand" "n")]
> UNSPEC_XXEVAL))]
> "TARGET_POWER10"
> --
ok
Thanks,
-Will
> 2.31.1
>
next prev parent reply other threads:[~2021-05-20 19:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 20:43 [PATCH 0/2] Move xx* builtins to vsx.md Michael Meissner
2021-05-18 20:46 ` [PATCH 1/2] " Michael Meissner
2021-05-20 19:30 ` will schmidt
2021-05-21 1:52 ` Michael Meissner
2021-05-24 15:58 ` Ping " Michael Meissner
2021-05-18 20:47 ` [PATCH 2/2] Fix xxeval predicates Michael Meissner
2021-05-20 19:31 ` will schmidt [this message]
2021-05-21 1:53 ` Michael Meissner
2021-05-24 16:02 ` Ping " Michael Meissner
2021-06-02 0:15 ` Michael Meissner
2021-06-02 0:13 ` Ping #2: [PATCH 0/2] Move xx* builtins to vsx.md 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=78c90b0ca123aeb85bfb60ff7c9a69180755049b.camel@vnet.ibm.com \
--to=will_schmidt@vnet.ibm.com \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=meissner@linux.ibm.com \
--cc=segher@kernel.crashing.org \
--cc=wschmidt@linux.ibm.com \
/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).