On 26/09/16 14:15, Christophe Lyon wrote:
Hi,
Sorry for the delay, I've been travelling.
On 27 July 2016 at 15:57, Ramana Radhakrishnan
<ramana....@googlemail.com> wrote:
On Tue, May 17, 2016 at 3:29 PM, Matthew Wahab
<matthew.wa...@foss.arm.com> wrote:
The handling of 16-bit integer data-movement in the ARM backend doesn't
make full use of the VFP instructions when they are available, even when
the values are for use in VFP operations.
This patch adds support for using the VFP instructions and registers
when moving 16-bit integer and floating point data between registers and
between registers and memory.
With this patch, I've noticed 2 regressions which still seem present on
trunk.
When GCC is configured with:
--target=arm-none-linux-gnueabihf --disable-libgomp
--disable-libmudflap --disable-libcilkrts --enable-checking
--enable-languages=c,c++,fortran --with-float=hard
--enable-build-with-cxx --with-mode=arm --with-cpu=cortex-a9
--with-fpu=vfp
and the tests run with -march=armv5t in RUNTESTFLAGS
FAIL: gcc.target/arm/constant-pool.c (test for excess errors)
because:
/ccepmUiD.s:29: Error: selected processor does not support ARM mode
`movw r0,4660'
FAIL: gfortran.fortran-torture/execute/nan_inf_fmt.f90 compilation, -O2
because:
/cc76h4mz.s: Assembler messages:
/cc76h4mz.s:413: Error: selected processor does not support ARM mode
`movw r3,8224'
/cc76h4mz.s:496: Error: selected processor does not support ARM mode
`movw r2,8224'
/cc76h4mz.s:578: Error: selected processor does not support ARM mode
`movw ip,8224'
Christophe
I suspect that this is the same MOVW problem as on the next patch in the series.
Matthew
