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][GCC][ARM] Generate .arch and .arch_extensions for each function if required. [Patch (3/3)]


Hi Christoph,

> >> > gcc/testsuite/
> >> > 2017-11-06  Tamar Christina  <tamar.christina@arm.com>
> >> >
> >> >     PR target/82641
> >> >     * gcc.target/arm/pragma_arch_attribute_2.c: New.
> >> >     * gcc.target/arm/pragma_arch_attribute_2.c: New.
> >> >     * gcc.target/arm/pragma_arch_attribute_3.c: New.
> >> >     * gcc.target/arm/pragma_fpu_attribute.c: New.
> >> >     * gcc.target/arm/pragma_fpu_attribute_2.c: New.
> >> >
> >> > --
> 
> I'm afraid you'll have to update the testcases: they fail on non-hf targets
> (arm-none-linux-gnueabi, arm-none-eabi), because:
> In file included from /gcc/testsuite/gcc.target/arm/pragma_fpu_attribute.c:7:
> /aci-gcc-fsf/builds/gcc-fsf-gccsrc/obj-arm-none-linux-
> gnueabi/gcc3/gcc/include/arm_neon.h:31:2:
> error: #error "NEON intrinsics not available with the soft-float ABI.
> Please use -mfloat-abi=softfp or -mfloat-abi=hard"
> /gcc/testsuite/gcc.target/arm/pragma_fpu_attribute.c:11:53: error:
> unknown type name 'poly64x1_t'
> /gcc/testsuite/gcc.target/arm/pragma_fpu_attribute.c:11:71: error:
> unknown type name 'poly64x1_t'

Well this is incredibly frustrating. I tested these configurations repeatedly locally:

Test Run By tnfchris on Thu Dec  7 13:39:54 2017                                                                                                                                                                                               
Target is arm-none-eabi
Host   is x86_64-pc-linux-gnu

/d/t/g/s/gcc (arm-implement-pragma-arch-verify ↩☡) grep "pragma_fpu_attribute\.c" ../../build-arm-none-eabi/results/vanilla/gcc.sum
PASS: gcc.target/arm/pragma_fpu_attribute.c (test for excess errors)
PASS: gcc.target/arm/pragma_fpu_attribute.c scan-assembler-times \\.fpu\\s+crypto-neon-fp-armv8 1
PASS: gcc.target/arm/pragma_fpu_attribute.c scan-assembler-times \\.fpu\\s+vfpv3-d16 1
PASS: gcc.target/arm/pragma_fpu_attribute.c (test for excess errors)
PASS: gcc.target/arm/pragma_fpu_attribute.c scan-assembler-times \\.fpu\\s+crypto-neon-fp-armv8 1
PASS: gcc.target/arm/pragma_fpu_attribute.c scan-assembler-times \\.fpu\\s+vfpv3-d16 1

--

Test Run By tnfchris on Thu Dec  7 11:08:29 2017
Native configuration is arm-none-linux-gnueabihf

tnfchris@native:~/gcc-arm$ grep "pragma_fpu_attribute\.c" ./gcc/testsuite/gcc/gcc.sum
PASS: gcc.target/arm/pragma_fpu_attribute.c (test for excess errors)
PASS: gcc.target/arm/pragma_fpu_attribute.c scan-assembler-times \\.fpu\\s+crypto-neon-fp-armv8 1
PASS: gcc.target/arm/pragma_fpu_attribute.c scan-assembler-times \\.fpu\\s+vfpv3-d16 1

So I'm quite surprised about this. In any case, I will look into it.

Thanks,
Tamar


> 
> Looking at other attributes tests, maybe you need to add arm_neon_ok?
> 
> Thanks,
> Christophe

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