This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH][ARM] NEON DImode immediate constants

From: Andrew Stubbs <ams at codesourcery dot com>
Cc: "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>, "patches at linaro dot org" <patches at linaro dot org>
Date: Fri, 27 Apr 2012 09:34:31 +0100
Subject: Re: [PATCH][ARM] NEON DImode immediate constants
References: <4F4CFEC6.2090705@codesourcery.com> <4F7595ED.8070900@codesourcery.com> <4F842ED0.3030206@codesourcery.com>

Ping.

On 10/04/12 14:00, Andrew Stubbs wrote:

Ping.

On 30/03/12 12:15, Andrew Stubbs wrote:

On 28/02/12 16:20, Andrew Stubbs wrote:

Hi all,

This patch implements 64-bit immediate constant loads in NEON.

The current state is that you can load const_vector, but not const_int.
This is clearly not ideal. The result is a constant pool entry when it's
not necessary.

The patch disables the movdi_vfp patterns for loading DImode values, if
the operand is const_int and NEON is enabled, and extends the neon_mov
pattern to include DImode const_int, as well as the const_vector
operands. I've modified neon_valid_immediate only enough to accept
const_int input - the logic remains untouched.


That patch failed to bootstrap successfully, but this updated patch
bootstraps and tests with no regressions.

OK?

Andrew

References:
- Re: [PATCH][ARM] NEON DImode immediate constants
  - From: Andrew Stubbs

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]