> Inside Google, there is a dedicated compiler team working on GNU
> Toolchain for various purposes including server-side
> computing, Android, Chrome OS, etc. Google engineers submit patches to
> upstream for public review and maintain the
> toolchain for Android.  Along with each Android Open Source Prokect
> (AOSP) release, there is a special branch in korg
> GIT [2] for hosting the GPL'd  toolchain source code modified by
> Google.  Usually, file "README.google" mentioned the
> summary, but it is not developer friendly because several changes were
> done within one GIT commit.
>
> Please refer to wiki for details:
>    https://wiki.linaro.org/Platform/Android/UpstreamToolchain
>

thats a good wiki page. thanks for the content. If I read the skia
example correctly, we could add a test to our "normal" abrek testsuite
that uses our daily android toolchain and run the skia benchmark? e.g.
we could start doing this benchmarking even without having a
validation solution ready for android targets?

Please let's talk to Paul how we can get the android toolchain to
/opt/android as part of abrek and lets try to add this to our abrek
testsuites. Until we have daily toolchain builds it would be OK to
download the android toolchain tarball from a fixed place from
people.linaro.org I guess.
I think there's going to be more to it than that.  My understand based on some quick research about skia is that it is a 2d graphics benchmark and needs to be run under android itself.  Which means we first need android booting on our hardware.  Am I mistaken about this?

Do we have any idea how far we are away from having linaro android images?

Thanks,
Paul Larson