public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Sandiford <richard.sandiford@linaro.org>
To: Tamar Christina <Tamar.Christina@arm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,  nd <nd@arm.com>,
	 James Greenhalgh <James.Greenhalgh@arm.com>,
	 "Marcus Shawcroft" <Marcus.Shawcroft@arm.com>,
	 Richard Earnshaw	<Richard.Earnshaw@arm.com>
Subject: Re: [PATCH][GCC][AArch64] optimize float immediate moves (2 /4) - HF/DF/SF mode.
Date: Wed, 14 Jun 2017 10:06:00 -0000	[thread overview]
Message-ID: <87mv9adgtb.fsf@linaro.org> (raw)
In-Reply-To: <VI1PR0801MB20316A7D3165E0EDD14CD43DFFCD0@VI1PR0801MB2031.eurprd08.prod.outlook.com>	(Tamar Christina's message of "Mon, 12 Jun 2017 07:31:50 +0000")

In addition to James's comments:

Tamar Christina <Tamar.Christina@arm.com> writes:
> +  [(const_int 0)]
> +  "{

"{ ... }" isn't necessary, we can just use { ... }

> +    unsigned HOST_WIDE_INT ival;
> +    if (!aarch64_reinterpret_float_as_int (operands[1], &ival))
> +      FAIL;
> +
> +    rtx tmp = gen_reg_rtx (SImode);
> +    aarch64_expand_mov_immediate (tmp, gen_int_mode (ival, SImode));
> +    tmp = simplify_gen_subreg (HImode, tmp, SImode, 0);

This looks wrong for big-endian, and...

> +    emit_move_insn (operands[0], gen_lowpart (HFmode, tmp));

...either it should be OK to go directly from tmp to the HFmode lowpart,
or we should move the HImode temporary into a fresh REG.  Current
validate_subreg seems to suggest that we need the latter.

Isn't it possible to use a HImode move immediate instead of an SImode one?

Thanks,
Richard

  reply	other threads:[~2017-06-14 10:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-07 11:38 Tamar Christina
2017-06-12  7:31 ` Tamar Christina
2017-06-14 10:06   ` Richard Sandiford [this message]
2017-06-15 13:25     ` Tamar Christina
2017-06-15 14:28       ` Tamar Christina
2017-06-16  7:53         ` Richard Sandiford
2017-06-16  8:42           ` Tamar Christina
2017-06-14  8:43 ` James Greenhalgh
2017-06-21 10:48   ` Tamar Christina
2017-06-26 10:50     ` Tamar Christina
2017-07-03  6:12       ` Tamar Christina
2017-07-10  7:35         ` Tamar Christina
2017-07-27 16:09       ` James Greenhalgh
2017-08-01 11:47       ` Bin.Cheng
2017-08-01 11:51         ` Tamar Christina
2017-08-01 12:04           ` Bin.Cheng

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=87mv9adgtb.fsf@linaro.org \
    --to=richard.sandiford@linaro.org \
    --cc=James.Greenhalgh@arm.com \
    --cc=Marcus.Shawcroft@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=Tamar.Christina@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nd@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).