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>,
"Kewen.Lin" <linkw@linux.ibm.com>,
David Edelsohn <dje.gcc@gmail.com>,
Peter Bergner <bergner@linux.ibm.com>
Subject: Re: [PATCH] Replace UNSPEC with RTL code for extendditi2.
Date: Fri, 13 May 2022 12:29:29 -0500 [thread overview]
Message-ID: <1f73a5822cd96e8f940d0212496562d6e49470f4.camel@vnet.ibm.com> (raw)
In-Reply-To: <Yn5wnicjLicdy3+a@toto.the-meissners.org>
On Fri, 2022-05-13 at 10:52 -0400, Michael Meissner wrote:
> Replace UNSPEC with RTL code for extendditi2.
>
Hi,
> When I submitted my patch on March 12th for extendditi2, Segher
> wished I
> had removed the use of the UNSPEC for the vextsd2q instruction. This
> patch rewrites extendditi2_vector to use VEC_SELECT rather than
> UNSPEC.
I'd suggest a paragraph break between the two sentences.
>
> 2022-05-13 Michael Meissner <meissner@linux.ibm.com>
>
> gcc/
> * config/rs6000/vsx.md (UNSPEC_EXTENDDITI2): Delete.
> (extendditi2_vector): Rewrite to use VEC_SELECT as a
> define_expand.
> (extendditi2_vector2): New insn.
Ok, so per my interpretation of the patch below, it converts the
define_insn extendditi2_vector into a define_expand, and creates a new
extendditi2_vector2 instruction.
Content below seems reasonable, I've not reviewed it extensively.
Thanks
-Will
> ---
> gcc/config/rs6000/vsx.md | 22 ++++++++++++++++++----
> 1 file changed, 18 insertions(+), 4 deletions(-)
>
> diff --git a/gcc/config/rs6000/vsx.md b/gcc/config/rs6000/vsx.md
> index a1a1ce95195..c091e5e2f47 100644
> --- a/gcc/config/rs6000/vsx.md
> +++ b/gcc/config/rs6000/vsx.md
> @@ -358,7 +358,6 @@ (define_c_enum "unspec"
> UNSPEC_VSX_FIRST_MISMATCH_EOS_INDEX
> UNSPEC_XXGENPCV
> UNSPEC_MTVSBM
> - UNSPEC_EXTENDDITI2
> UNSPEC_VCNTMB
> UNSPEC_VEXPAND
> UNSPEC_VEXTRACT
> @@ -5083,10 +5082,25 @@ (define_insn_and_split "extendditi2"
> (set_attr "type" "shift,load,vecmove,vecperm,load")])
>
> ;; Sign extend 64-bit value in TI reg, word 1, to 128-bit value in
> TI reg
> -(define_insn "extendditi2_vector"
> +(define_expand "extendditi2_vector"
> + [(use (match_operand:TI 0 "gpc_reg_operand"))
> + (use (match_operand:TI 1 "gpc_reg_operand"))]
> + "TARGET_POWER10"
> +{
> + rtx dest = operands[0];
> + rtx src_v2di = gen_lowpart (V2DImode, operands[1]);
> + rtx element = GEN_INT (VECTOR_ELEMENT_SCALAR_64BIT);
> +
> + emit_insn (gen_extendditi2_vector2 (dest, src_v2di, element));
> + DONE;
> +})
> +
> +(define_insn "extendditi2_vector2"
> [(set (match_operand:TI 0 "gpc_reg_operand" "=v")
> - (unspec:TI [(match_operand:TI 1 "gpc_reg_operand" "v")]
> - UNSPEC_EXTENDDITI2))]
> + (sign_extend:TI
> + (vec_select:DI
> + (match_operand:V2DI 1 "gpc_reg_operand" "v")
> + (parallel [(match_operand 2 "vsx_scalar_64bit" "wD")]))))]
> "TARGET_POWER10"
> "vextsd2q %0,%1"
> [(set_attr "type" "vecexts")])
> --
> 2.35.3
>
>
next prev parent reply other threads:[~2022-05-13 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 14:52 Michael Meissner
2022-05-13 17:29 ` will schmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-01 16:59 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=1f73a5822cd96e8f940d0212496562d6e49470f4.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=linkw@linux.ibm.com \
--cc=meissner@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).