While doing some arm-none-eabi testing, I noticed that a bunch of
gcc.dg/vect tests were causing the target to hang from trying to execute
code compiled with "-mfpu=neon -mfloat-abi=softfp", on a target that
doesn't support those instructions. And, this was caused by tests
specifying "dg-do ru
On Sep 25, 2014, at 1:04 PM, Sandra Loosemore wrote:
> While doing some arm-none-eabi testing, I noticed that a bunch of gcc.dg/vect
> tests were causing the target to hang from trying to execute code compiled
> with "-mfpu=neon -mfloat-abi=softfp", on a target that doesn't support those
> inst
On 09/25/2014 02:04 PM, Sandra Loosemore wrote:
While doing some arm-none-eabi testing, I noticed that a bunch of
gcc.dg/vect tests were causing the target to hang from trying to execute
code compiled with "-mfpu=neon -mfloat-abi=softfp", on a target that
doesn't support those instructions. And,
On 09/25/2014 04:48 PM, Sandra Loosemore wrote:
> On 09/25/2014 02:04 PM, Sandra Loosemore wrote:
>> While doing some arm-none-eabi testing, I noticed that a bunch of
>> gcc.dg/vect tests were causing the target to hang from trying to execute
>> code compiled with "-mfpu=neon -mfloat-abi=softfp", o
