From: James Greenhalgh <james.greenhalgh@arm.com>
To: Kyrill Tkachov <kyrylo.tkachov@arm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Marcus Shawcroft <Marcus.Shawcroft@arm.com>,
Richard Earnshaw <Richard.Earnshaw@arm.com>
Subject: Re: [PATCH][AArch64] Use preferred aliases for CSNEG, CSINC, CSINV
Date: Fri, 11 Sep 2015 15:38:00 -0000 [thread overview]
Message-ID: <20150911153146.GA5206@arm.com> (raw)
In-Reply-To: <55E5790A.2090205@arm.com>
On Tue, Sep 01, 2015 at 11:08:10AM +0100, Kyrill Tkachov wrote:
> Hi all,
>
> The ARMv8-A reference manual says:
> "CNEG <Wd>, <Wn>, <cond>
> is equivalent to
> CSNEG <Wd>, <Wn>, <Wn>, invert(<cond>)
> and is the preferred disassembly when Rn == Rm && cond != '111x'."
>
> That is, when the two input registers are the same we can use the shorter CNEG mnemonic
> with the inverse condition instead of the longer CSNEG instruction. Similarly for the
> CSINV and CSINC instructions, they have shorter CINV and CINC forms.
> This patch adjusts the output templates to emit the preferred shorter sequences when possible.
>
> The new mnemonics are just aliases, they map down to the same instruction in the end, so there
> are no performance or behaviour implications. But it does make the assembly a bit more readable
> IMO, since:
> "cneg w27, w9, le"
> can be simply read as "if the condition is less or equal negate w9" instead of the previous:
> "csneg w27, w9, w9, gt" where you have to remember which of the input registers is negated.
>
>
> Bootstrapped and tested on aarch64-linux-gnu.
> Ok for trunk?
>
> diff --git a/gcc/config/aarch64/aarch64.md b/gcc/config/aarch64/aarch64.md
> index 77bc7cd..2e4b26c 100644
> --- a/gcc/config/aarch64/aarch64.md
> +++ b/gcc/config/aarch64/aarch64.md
> @@ -3090,7 +3090,12 @@ (define_insn "csinc3<mode>_insn"
> (const_int 1))
> (match_operand:GPI 3 "aarch64_reg_or_zero" "rZ")))]
> ""
> - "csinc\\t%<w>0, %<w>3, %<w>2, %M1"
> + {
> + if (rtx_equal_p (operands[2], operands[3]))
> + return "cinc\\t%<w>0, %<w>2, %m1";
> + else
> + return "csinc\\t%<w>0, %<w>3, %<w>2, %M1";
> + }
> [(set_attr "type" "csel")]
> )
I guess you do it this way rather than just adding a new alternative in
the pattern to avoid any chance of constraining the register allocator, but
would this not be more natural to read as an {r, r, r, 2} alternative, or
similar?
If you've given that some thought and decided it doesn't work for you,
then this is OK for trunk.
Thanks,
James
next prev parent reply other threads:[~2015-09-11 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 10:08 Kyrill Tkachov
2015-09-11 15:26 ` Kyrill Tkachov
2015-09-11 15:38 ` James Greenhalgh [this message]
2015-09-11 16:29 ` Kyrill Tkachov
2015-09-12 2:04 ` Andrew Pinski
2015-09-21 13:25 ` Kyrill Tkachov
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=20150911153146.GA5206@arm.com \
--to=james.greenhalgh@arm.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrylo.tkachov@arm.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).