On 8 March 2011 02:37, Jim Huang wrote:
> I just updated wiki page about Google's compiler benchmark suite:
> https://wiki.linaro.org/Platform/Android/UpstreamToolchain
> Please check the section, "Evaluate Benchmark suite".
> Through adb[1], it is highly convenient to bench generated binary
>
On Tue, Mar 8, 2011 at 7:37 AM, Jim Huang wrote:
> From the above messages, Google introduced the automated approach to deploy
> benchmark suite and evaluate it on the fly.
Hi jserv. That's quite cool. I'll have a look into their benchmark
suite as there seems to be a lot of overlap with what I
On 2 March 2011 09:51, Michael Hope wrote:
> On Tue, Mar 1, 2011 at 3:53 PM, Jim Huang wrote:
[...]
>> 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.gi
On Tue, Mar 1, 2011 at 3:53 PM, Jim Huang wrote:
> On 1 March 2011 10:45, Michael Hope 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,
>
> Tha
On 1 March 2011 18:07, Andrew Stubbs wrote:
> On 01/03/11 07:00, Jim Huang wrote:
>>> I think thats fine. however, how do we ensure that we have patches
>>> > that always apply to both release/snapshots? do we maintain branches
>>> > for gcc-patches.git in case you need two versions of patch X i
On 01/03/11 07:00, Jim Huang wrote:
I think thats fine. however, how do we ensure that we have patches
> that always apply to both release/snapshots? do we maintain branches
> for gcc-patches.git in case you need two versions of patch X if the
> linaro gcc codebase diverged?
I might need help
On 25 February 2011 22:28, Alexander Sack wrote:
> On Wed, Feb 23, 2011 at 8:28 AM, Jim Huang wrote:
>> I would like to make a proposal about utilizing Linaro toolchain for
>> Android and NDK (Native Development Kit)[1].
Added linaro-toolchai list in Cc.
>> ** Motivation
>>
>> There are some di
The skia code is also hold in the chromium project. I used chromium web
browser to check the skia performance with some browser benchmarks.
I think pixman is also a good candidate for skia to benchmark toolchain.
Regards,
Jammy
On Tue, Mar 1, 2011 at 10:53 AM, Jim Huang wrote:
> On 1 March 201
On 1 March 2011 10:45, Michael Hope 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/ w
On Tue, Mar 1, 2011 at 4:32 AM, Jesse Barker wrote:
> FWIW, skia certainly isn't android only and, at least for the purposes of
> getting the validation side of things up and running, could be run on a
> non-android build (Jammy is likely doing something like this for his work,
> though not orient
FWIW, skia certainly isn't android only and, at least for the purposes of
getting the validation side of things up and running, could be run on a
non-android build (Jammy is likely doing something like this for his work,
though not oriented at abrek at the moment). Of course, I could be
over-simpl
> 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
On Wed, Feb 23, 2011 at 8:28 AM, Jim Huang wrote:
> Hello list,
>
> I would like to make a proposal about utilizing Linaro toolchain for
> Android and NDK (Native Development Kit)[1].
>
> ** Motivation
>
> There are some different perspectives between Linaro toolchain and
> Google Android toolchai
Hello list,
I would like to make a proposal about utilizing Linaro toolchain for
Android and NDK (Native Development Kit)[1].
** Motivation
There are some different perspectives between Linaro toolchain and
Google Android toolchain including technical and
non-technical considerations. It doesn'
14 matches
Mail list logo
