public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Bin.Cheng" <amker.cheng@gmail.com>
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 (1 /4) - infrastructure.
Date: Tue, 01 Aug 2017 11:16:00 -0000	[thread overview]
Message-ID: <CAHFci28i+-+EDpd0UAEPhd7JXT+x9VE-mUmUYv1f7hP6nNT-qQ@mail.gmail.com> (raw)
In-Reply-To: <VI1PR0801MB203164A5E1F6B6EDA0F2074AFFC80@VI1PR0801MB2031.eurprd08.prod.outlook.com>

On Wed, Jun 7, 2017 at 12:38 PM, Tamar Christina
<Tamar.Christina@arm.com> wrote:
> Hi All,
>
>
> This patch lays the ground work to fix the immediate moves for floats
> to use a combination of mov, movi, fmov instead of ldr and adrp to load
> float constants that fit within the 16-bit limit of movz.
>
> The idea behind it is that these are used quite often in masks etc and we can
> get a gain by doing integer moves instead of memory loads.
>
> This patch also adds the patterns for SImode and DImode to use SIMD mov
> instructions when it's able to.
>
> It's particularly handy when masks are used such as the
> 0x80000000 mask in copysignf.
>
> This now generates
>
>         movi    v2.2s, 0x80, lsl 24
>
> instead of a literal load.
>
>
> Regression tested on aarch64-none-linux-gnu and no regressions.
Hi,
I saw below failure after svn+ssh://gcc.gnu.org/svn/gcc/trunk@250672

FAIL: gcc.target/aarch64/advsimd-intrinsics/vcvt_high_1.c   -O1
(internal compiler error)

Regression in patch updates?

Thanks,
bin
>
> OK for trunk?
>
> Thanks,
> Tamar
>
>
> gcc/
> 2017-06-07  Tamar Christina  <tamar.christina@arm.com>
>
>         * config/aarch64/aarch64.c
>         (aarch64_simd_container_mode): Add prototype.
>         (aarch64_expand_mov_immediate): Add HI support.
>         (aarch64_reinterpret_float_as_int, aarch64_float_const_rtx_p: New.
>         (aarch64_can_const_movi_rtx_p): New.
>         (aarch64_preferred_reload_class):
>         Remove restrictions of using FP registers for certain SIMD operations.
>         (aarch64_rtx_costs): Added new cost for CONST_DOUBLE moves.
>         (aarch64_valid_floating_const): Add integer move validation.
>         (aarch64_simd_imm_scalar_p): Remove.
>         (aarch64_output_scalar_simd_mov_immediate): Generalize function.
>         (aarch64_legitimate_constant_p): Expand list of supported cases.
>         * config/aarch64/aarch64-protos.h
>         (aarch64_float_const_rtx_p, aarch64_can_const_movi_rtx_p): New.
>         (aarch64_reinterpret_float_as_int): New.
>         (aarch64_simd_imm_scalar_p): Remove.
>         * config/aarch64/predicates.md (aarch64_reg_or_fp_float): New.
>         * config/aarch64/constraints.md (Uvi): New.
>         (Dd): Split into Ds and new Dd.
>         * config/aarch64/aarch64.md (*movsi_aarch64):
>         Add SIMD mov case.
>         (*movdi_aarch64): Add SIMD mov case.

  parent reply	other threads:[~2017-08-01 11:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-07 11:38 Tamar Christina
2017-06-08 10:32 ` Richard Sandiford
2017-06-12  7:29   ` Tamar Christina
2017-06-13 16:39     ` James Greenhalgh
2017-06-13 17:08       ` Richard Sandiford
2017-06-15 12:50       ` Tamar Christina
2017-06-26 10:49         ` Tamar Christina
2017-07-03  6:12           ` Tamar Christina
2017-07-10  7:35             ` Tamar Christina
2017-07-19 15:49           ` James Greenhalgh
2017-07-26 16:01             ` Tamar Christina
2017-07-27 15:43               ` James Greenhalgh
2017-07-28 15:06                 ` Tamar Christina
2017-08-01 11:16 ` Bin.Cheng [this message]
2017-08-01 11:19   ` Tamar Christina

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=CAHFci28i+-+EDpd0UAEPhd7JXT+x9VE-mUmUYv1f7hP6nNT-qQ@mail.gmail.com \
    --to=amker.cheng@gmail.com \
    --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).