Michael Hope wrote:
> It's only part of the puzzle, but I run speed benchmarks as part of
> the continious build:
> http://ex.seabright.co.nz/helpers/buildlog
> http://ex.seabright.co.nz/helpers/benchcompare
>
> http://ex.seabright.co.nz/build/gcc-linaro-4.5-2010.09-1/logs/armv7l-maverick-cbuild4-pavo4/pybench-test.txt
>
> I've just modified this to build different variants as well. ffmpeg
> now builds as supplied (-O2 and others), with -Os, with hand-written
> assembler turned off, and with -mfpu=neon. corebench builds in -O2
> and -Os.
Here are some options we may have to use in our benchmarks,
{-Os,-O2} -fno-common -mthumb --mfloat-abi={hard,soft} -mfpu=neon
IIRC, hardfp will increase the code size to some extent.
>
> This might be one way to approach things. It's simple to add other
> programs into the mix.
>
> -- Michael
>
> On Fri, Sep 17, 2010 at 4:05 AM, Dave Martin <dave.mar...@linaro.org> wrote
--
Yao Qi
CodeSourcery
y...@codesourcery.com
(650) 331-3385 x739
_______________________________________________
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
