On Wed, Sep 15, 2010 at 09:49:34PM +0800, Yao Qi wrote:
> * Results
I got this GCC PR by accident today.
PR16996 [meta-bug] code size improvements
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16996
We can get most of code size bugs through it, and most of these bugs
are about ARM.
--
Yao Qi
Code
Hi,
about the status of binutils testsuite Thumb coverage (CS204 in the
workplan), I have filed two Launchpad bugs:
#640263: Testsuite coverage: Thumb-2 VFP/NEON encodings
https://bugs.launchpad.net/binutils-linaro/+bug/640263
#640272: Testsuite coverage: Thumb relocations
https://bugs.launchpad
> GLIBC a mechanism for picking the best routines to use based on the
> CPU capabilities. This means that GLIBC can include A8 and A9
> versions both with and without NEON, Ubuntu can ship all of these
> versions, and the dynamic linker can choose the best one based on the
> chip it is running on
On 16/09/10 09:23, Chung-Lin Tang wrote:
> Hi,
> about the status of binutils testsuite Thumb coverage (CS204 in the
> workplan), I have filed two Launchpad bugs:
Thanks Chung-Lin. :)
Andrew
___
linaro-toolchain mailing list
linaro-toolchain@lists.lina
On Wed, Sep 15, 2010, Michael Hope wrote:
> GLIBC a mechanism for picking the best routines to use based on the
> CPU capabilities. This means that GLIBC can include A8 and A9
> versions both with and without NEON, Ubuntu can ship all of these
> versions, and the dynamic linker can choose the best
Hi,
On Thu, Sep 16, 2010 at 11:43 AM, Loïc Minier wrote:
[...]
> Are you sure we have an auxv entry for a8 versus a9? In any case, I
> doubt it's considered for glibc hwcaps right now as this requires
> explicit flagging and the list of ARM flags is quite short.
Currently, I believe this i
It would be interesting if we could get a good, representative set of
comparative benchmarks for the size and performance impact of -Os.
I did a bit of investigation here:
https://wiki.linaro.org/Platform/Foundations/OptimiseForSize
(though with just a few packages and only one benchmark, it's n
I think that it is easier to describe situation in email then on irc.
Currently there are 4 packages related to cross compilation support:
- armel-cross-toolchain-base (a-c-t-base in short)
- gcc-4.4-armel-cross
- gcc-4.5-armel-cross
- gcc-defaults-armel-cross
Each of them got into archive but
Hi Marcin,
Thanks for whipping these packages into shape!
On Thu, Sep 16, 2010 at 06:19:28PM +0200, Marcin Juszkiewicz wrote:
> 1. a-c-t-base is at 1.47 in archive and was built from gcc-4.5-source
>4.5.1-6ubuntu1 version. This package is used to bootstrap armel cross
>toolchain and gener
xf. http://lists.linaro.org/pipermail/linaro-toolchain/2010-August/69.html
> It is not upstreamable due to copyright issues, but we have a policy
> that we can keep such patches, if we wish.
I wrote this patch. If I am the copyright issue, then there is no issue.
I have a copyright assignmen
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
11 matches
Mail list logo