On 02/11/15 09:20, Kyrill Tkachov wrote:
> 
> On 02/11/15 08:38, Ramana Radhakrishnan wrote:
>>>>> 2015-10-12  Kyrylo Tkachov  <kyrylo.tkac...@arm.com>
>>>>>
>>>>>      PR target/67929
>>>>>      * gcc.target/arm/pr67929_1.c: New test.
>>> This test fails when tested on hard-float targets, adding the
>>> following line to avoid testing it in such cases will fix the issue,
>>> but I wonder if there is a better dejaGNU directives sequence to do
>>> that.
>>>
>>> /* { dg-skip-if "avoid conflicting multilib options" { *-*-*eabihf } {
>>> "*" } { "" } } */
>> No, not without further investigation into why the test is failing.
> 
> I believe it's the same issue that Christophe reported
> in the comment for https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67929.
> It's because /* { dg-add-options arm_vfp3 } */ added -mfloat-abi=softfp but
> the crt* files were compiled for hardfp. It's a testism.
> I think adding an explicit -mfloat-abi=hard and gating on arm_hard_vfp_ok?

No, see my other response. 

Looking at it again, I can't see anything ARM specific in the source
that causes this to remain in gcc.target/arm.

Instead remove all the special casing and move it into gcc.c-torture/execute.

regards
Ramana

> 
>> regards
>> Ramana
>>
>>> Cheers,
>>> Yvan
>>>
> 

Reply via email to