From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jiufu Guo <guojiufu@linux.ibm.com>
Cc: gcc-patches@gcc.gnu.org, dje.gcc@gmail.com, linkw@gcc.gnu.org,
meissner@linux.ibm.com
Subject: Re: [PATCH 1/2] Using pli(paddi) and rotate to build 64bit constants
Date: Fri, 2 Sep 2022 11:12:36 -0500 [thread overview]
Message-ID: <20220902161236.GQ25951@gate.crashing.org> (raw)
In-Reply-To: <7eedwuw9gq.fsf@pike.rch.stglabs.ibm.com>
Hi!
On Fri, Sep 02, 2022 at 02:56:21PM +0800, Jiufu Guo wrote:
> >> + /* pli 9,high32 + sldi 9,32 + paddi 9,9,low32. */
> >> + else
> >> + {
> >
> > The comment goes here, in the block it refers to. Comments for a block
> > are the first thing *in* the block.
> OK, great! I like the format you sugguested here :-)
It's the normal GCC style, not my invention :-)
> >> + emit_move_insn (copy_rtx (dest), GEN_INT ((ud4 << 16) | ud3));
> >> +
> >> + emit_move_insn (copy_rtx (dest),
> >> + gen_rtx_ASHIFT (DImode, copy_rtx (dest),
> >> + GEN_INT (32)));
> >> +
> >> + bool can_use_paddi = REGNO (dest) != FIRST_GPR_REGNO;
> >
> > There should be a test that we so the right thing (or *a* right thing,
> > anyway; a working thing; but hopefully a reasonably fast thing) for
> > !can_use_paddi.
> To catch this test point, we need let the splitter run after RA,
> and register 0 happen to be the dest of an assignment.
Or force the testcase to use r0 some other way. Well, "forcing" cannot
be done, but we can probably encourage it (via a local register asm for
example, or by tying the var to the output of an asm that is hard reg 0,
or perhaps there are other ways as well :-) )
> I will add this test case in patch.
> Is this ok? Any sugguestions?
Sounds useful yes. Maybe describe the expected output in words as well
(in the testcase, not in email)?
> >> +/* 3 insns for each constant: pli+sldi+paddi or pli+pli+rldimi.
> >> + And 3 additional insns: std+std+blr: 9 insns totally. */
> >> +/* { dg-final { scan-assembler-times {(?n)^\s+[a-z]} 9 } } */
> >
> > Also test the expected insns separately please? The std's (just with
> > \mstd so it will catch all variations as well), the blr, the pli's and
> > the rldimi etc.?
> The reason of using "(?n)^\s+[a-z]" is to keep this test case pass no
> matter the splitter running before or after RA.
Ah. Some short comment in the testcase please?
Thanks again,
Segher
next prev parent reply other threads:[~2022-09-02 16:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 3:24 Jiufu Guo
2022-09-01 21:52 ` Segher Boessenkool
2022-09-02 6:56 ` Jiufu Guo
2022-09-02 16:12 ` Segher Boessenkool [this message]
2022-09-05 6:25 ` Jiufu Guo
2022-09-05 13:42 ` Segher Boessenkool
2022-09-06 12:34 ` Jiufu Guo
2022-09-02 15:29 ` Peter Bergner
2022-09-02 16:20 ` Segher Boessenkool
2022-09-02 4:07 ` Kewen.Lin
2022-09-05 6:22 ` Jiufu Guo
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=20220902161236.GQ25951@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=meissner@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).