On Tue, Nov 9, 2010 at 11:08 AM, Julian Brown <email address hidden> wrote:
> I can't find a bug here, apart from perhaps that the test case
> (gcc/testsuite/gcc.target/arm/neon-load-df0.c) is not written very
> robustly. The compiler is making a sane choice when compiling that test:
> there's no particular need to use a NEON register for the operation in
> question, whether or not the hard-float ABI is in use. An alternative
> test case, e.g. simply:
>
> double bar ()
> {
> return 0.0;
> }
>
> compiled with -mfloat-abi=hard, reveals that the load-double-zero patch
> does work correctly (in a case where using a NEON register is definitely
> beneficial).
>
how about -mfloat-abi=soft-fp ? thats where we see the problem.
It will take some time to pin down the problem in cairo. Let me try to
gather details
and see if we can have something put together.
> --
> Optimize load 0.0 for NEON seems not to work
> https://bugs.launchpad.net/bugs/667490
> You received this bug notification because you are a direct subscriber
> of the bug.
>
On Tue, Nov 9, 2010 at 11:08 AM, Julian Brown <email address hidden> wrote: gcc.target/ arm/neon- load-df0. c) is not written very
> I can't find a bug here, apart from perhaps that the test case
> (gcc/testsuite/
> robustly. The compiler is making a sane choice when compiling that test:
> there's no particular need to use a NEON register for the operation in
> question, whether or not the hard-float ABI is in use. An alternative
> test case, e.g. simply:
>
> double bar ()
> {
> return 0.0;
> }
>
> compiled with -mfloat-abi=hard, reveals that the load-double-zero patch
> does work correctly (in a case where using a NEON register is definitely
> beneficial).
>
how about -mfloat-abi=soft-fp ? thats where we see the problem. /bugs.launchpad .net/bugs/ 667490
It will take some time to pin down the problem in cairo. Let me try to
gather details
and see if we can have something put together.
> --
> Optimize load 0.0 for NEON seems not to work
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>