public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kyrill Tkachov <kyrylo.tkachov@arm.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Marcus Shawcroft <Marcus.Shawcroft@arm.com>,
	 James Greenhalgh <James.Greenhalgh@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:26:00 -0000	[thread overview]
Message-ID: <55F2F27A.3000606@arm.com> (raw)
In-Reply-To: <55E5790A.2090205@arm.com>

Ping.
https://gcc.gnu.org/ml/gcc-patches/2015-09/msg00020.html

Thanks,
Kyrill

On 01/09/15 11:08, 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?
>
> Thanks,
> Kyrill
>
> 2015-09-01  Kyrylo Tkachov  <kyrylo.tkachov@arm.com>
>
>       * config/aarch64/aarch64.md (csinc3<mode>_insn): Use CINC
>       mnemonic when possible.
>       (*csinv3<mode>_insn): Use CINV mnemonic when possible.
>       (csneg3<mode>_insn): USE CNEG mnemonic when possible.
>
> 2015-09-01  Kyrylo Tkachov  <kyrylo.tkachov@arm.com>
>
>       * gcc.target/aarch64/abs_1.c: Update scan-assembler checks
>       to allow cneg.
>       * gcc.target/aarch64/cond_op_imm_1.c: Likewise.  Likewise for cinv.
>       * gcc.target/aarch64/mod_2.c: Likewise.

  reply	other threads:[~2015-09-11 15:25 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 [this message]
2015-09-11 15:38 ` James Greenhalgh
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=55F2F27A.3000606@arm.com \
    --to=kyrylo.tkachov@arm.com \
    --cc=James.Greenhalgh@arm.com \
    --cc=Marcus.Shawcroft@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=gcc-patches@gcc.gnu.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).