On Tue, Mar 1, 2011 at 3:53 PM, Jim Huang jim.huang@linaro.org wrote:
On 1 March 2011 10:45, Michael Hope michael.hope@linaro.org wrote: [...]
I'd like to use Skia as a toolchain benchmark but the upstream seems a bit messy. I'm using this export: http://people.linaro.org/~michaelh/skia-0~svn788.tar.xz
hi Michael,
Thanks for your interest!
from http://code.google.com/p/skia/ which I then build and run using these rules: http://bazaar.launchpad.net/~linaro-toolchain-dev/cbuild/trunk/view/head:/li...
The code.google version seems a bit broken. autoconf scripts are included but they don't work. The non-autoconf Makefile assumes Intel with SSE2. The Android Skia seems to be a fork from some time ago and uses build scripts that are tightly tied into the Android build system.
Yes, don't use autotool inside skia package.
What's the best version to use? I'd like to standardise across Linaro for benchmarking so that results can be compared across groups, or at least so we don't get confused.
The skia maintainer, Mike Reed, made two branches: one is hosted in Google Code, and another is inside Android source tree: http://android.git.kernel.org/?p=platform/external/skia.git%3Ba=summary
I would suggest to use the later.
Thanks Jim. The Android tree doesn't have any build scripts and I'm reluctant to stray too far away from upstream by adding my own. I'll stick with the code.google one for now.
I've updated: http://bazaar.launchpad.net/~linaro-toolchain-dev/cbuild/trunk/view/head:/li...
with interations so that each sub benchmark runs for approximately five seconds. This reduces the noise in the results, although I haven't checked to see if some of the very fast ones like fps_fill are dominated by the test harness overhead.
For example, running: bench -rotate -scale -clip -config 8888 -repeat 600 -match fps_blend
will take around 5 s to complete on a 1 GHz Cortex-A9.
-- Michael