On 01/12/17 15:43, Charles Baylis wrote:
On 30 November 2017 at 15:56, Kyrill Tkachov
wrote:
So is it the case that you don't run any arm tests that include arm_neon.h
in your configuration?
No, it is only the case that any arm test which includes arm_neon.h
(in fact, any system header) *an
On 30 November 2017 at 15:56, Kyrill Tkachov
wrote:
>
> So is it the case that you don't run any arm tests that include arm_neon.h
> in your configuration?
No, it is only the case that any arm test which includes arm_neon.h
(in fact, any system header) *and* uses dg-add-options
-mfloat-abi=hard
On 27/11/17 19:23, Charles Baylis wrote:
On 27 November 2017 at 17:47, Kyrill Tkachov
wrote:
Hi Charles,
On 27/11/17 17:03, Charles Baylis wrote:
Some of the new tests in addr-modes-float.c, which were introduced for
the rework of addressing modes costs [1] fail when GCC is configured
to de
On 27 November 2017 at 17:47, Kyrill Tkachov
wrote:
> Hi Charles,
>
> On 27/11/17 17:03, Charles Baylis wrote:
>>
>> Some of the new tests in addr-modes-float.c, which were introduced for
>> the rework of addressing modes costs [1] fail when GCC is configured
>> to default to a softfp calling con
Hi Charles,
On 27/11/17 17:03, Charles Baylis wrote:
Some of the new tests in addr-modes-float.c, which were introduced for
the rework of addressing modes costs [1] fail when GCC is configured
to default to a softfp calling convention. Fix this by annotating the
test functions with __attribute__
Some of the new tests in addr-modes-float.c, which were introduced for
the rework of addressing modes costs [1] fail when GCC is configured
to default to a softfp calling convention. Fix this by annotating the
test functions with __attribute__((pcs("aapcs-vfp"))).
Thanks to Christophe for pointing
