From: Segher Boessenkool <segher@kernel.crashing.org>
To: luoxhu <luoxhu@linux.ibm.com>
Cc: gcc-patches@gcc.gnu.org, dje.gcc@gmail.com,
wschmidt@linux.ibm.com, guojiufu@linux.ibm.com,
linkw@gcc.gnu.org
Subject: Re: [PATCH] rs6000: Split movsf_from_si from high word before reload[PR89310]
Date: Tue, 7 Jul 2020 16:31:16 -0500 [thread overview]
Message-ID: <20200707213116.GU3598@gate.crashing.org> (raw)
In-Reply-To: <66c7b5d6-afa6-53d7-704d-44834ff00311@linux.ibm.com>
Hi!
On Tue, Jul 07, 2020 at 04:39:58PM +0800, luoxhu wrote:
> > Lots of questions, sorry!
>
> Thanks for the nice suggestions of the initial patch contains many issues:),
Pretty much all of it should *work*, it just can be improved and
simplified quite a bit :-)
> For this case, %1:SF matches with "=wa"? And how to construct cases to
> match("=?r", "wa") and ("=!r", "r") combinations, please?
operands[0], not operands[1]?
Simple testcases will not put the output into a GPR, unless you force
the compiler to do that, because of the ? and !.
Often you can just do
asm("#" : "+r"(x));
to force "x" into a GPR at that point of the program. But there is
nothing stopping the compiler from copying it back to a VSR where it
thinks that is cheaper ;-)
So maybe this pattern should just have the GPR-to-VSR alternative? It
does not look like the GPR destination variants are useful?
> + rtx op0 = operands[0];
> + rtx op1 = operands[1];
> + rtx op2 = operands[2];
(Please just write out operands[N] everywhere).
> + if (GET_CODE (operands[2]) == SCRATCH)
> + op2 = gen_reg_rtx (DImode);
> +
> + rtx mask = GEN_INT (HOST_WIDE_INT_M1U << 32);
> + emit_insn (gen_anddi3 (op2, op1, mask));
Groovy :-)
So, it looks like you can remove the ? and ! alternatives, leaving just
the first alternative?
Segher
next prev parent reply other threads:[~2020-07-07 21:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 2:17 Xionghu Luo
2020-07-07 0:18 ` Segher Boessenkool
2020-07-07 8:39 ` luoxhu
2020-07-07 21:31 ` Segher Boessenkool [this message]
2020-07-08 3:19 ` luoxhu
2020-07-08 22:43 ` Segher Boessenkool
2020-07-09 3:09 ` luoxhu
2020-07-09 19:25 ` Segher Boessenkool
2020-07-10 1:39 ` [PATCH] rs6000: Define movsf_from_si2 to extract high part SF element from DImode[PR89310] luoxhu
2020-07-11 0:54 ` Segher Boessenkool
2020-07-13 6:30 ` luoxhu
2020-07-14 14:17 ` David Edelsohn
2020-07-15 3:47 ` luoxhu
2020-07-20 15:31 ` Segher Boessenkool
2020-07-21 3:43 ` luoxhu
2020-07-10 7:41 ` [PATCH] rs6000: Split movsf_from_si from high word before reload[PR89310] luoxhu
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=20200707213116.GU3598@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=guojiufu@linux.ibm.com \
--cc=linkw@gcc.gnu.org \
--cc=luoxhu@linux.ibm.com \
--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).