> At the moment good 'ol
> CoreMark is worse with -O3 -omfpu=neon...
It maybe worth to try -fvect-cost-model.
Ira
>
> -- Michael
>
> ___
> linaro-toolchain mailing list
> linaro-toolchain@lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/l
On Sun, May 22, 2011 at 9:05 PM, Ira Rosen wrote:
>
>
>> At the moment good 'ol
>> CoreMark is worse with -O3 -omfpu=neon...
>
> It maybe worth to try -fvect-cost-model.
Worse again I'm afraid. -O3 -mfpu=neon scores 99 % of -O3. -O3
-mfpu=neon -fvect-cost-model scores 96 %.
-- Michael
__
On Fri, May 20, 2011 at 7:33 PM, Richard Sandiford
wrote:
> Michael Hope writes:
>> How about also 'Ensure vectorised code doesn't regress over
>> non-vectorised code'? The goal would be for 90 % of benchmarks to not
>> regress and 99 % to regress no more than 2 %. At the moment good 'ol
>> Cor
== Last week ==
* Took Monday off, flew back to Taiwan on Tues., got home Wed. night.
* LP:689887, ICE in get_arm_condition_code(). Finally have some new
progress on this. Found my code was rejecting DImode comparisons,
causing uses of __aeabi_lcmp, etc. in expanded RTL. While this still
does not
