linaro-toolchain

linaro-toolchain@lists.linaro.org

2 participants
5601 discussions

by Christian Robottom Reis

In case nobody here caught it: https://lwn.net/Articles/512548/ Interesting? Worth talking to Andi about it for ARM? -- Christian Robottom Reis | [+55 16] 3376 0125 | http://async.com.br/~kiko Async Open Source | [+55 16] 9112 6430 | http://launchpad.net/~kiko

12 years, 10 months

[ACTIVITY] Aug 21-Aug 24

by Christophe Lyon

== Progress == * Fixed problems with my patch for "constant vec permute operation for the vext instruction" blue-print, validated in cbuild. * Ported it to trunk and submitted for review. R.Earnshaw requested validation on big-endian. I need to upgrade my qemu to have it supported. * Compiled my Neon intrinsics testsuite with LLVM (version 3.2 trunk 160543). It compiles at O0/O1/O2/O3, but only O0 produces the expected results. Errors include: vset_lane, vld3, and vld4. * Started looking a bswap16 support == Next == * Have my "constant vec permute operation for the vext instruction" patch accepted on trunk * Continue with bswap16 support.

12 years, 10 months

[ACTIVITY] 20 August - 24 August

by Matthew Gretton-Dann

== Progress == * Follow up from 2012.08 Toolchain release * Updated Wiki pages * Start working on symbol_ref split benchmarking. * Backport to PR54212 done upstream to 4.6 and 4.7 * Started picking up Hot/Cold partitioning in PGO blueprint: * https://blueprints.launchpad.net/gcc-linaro/+spec/hot-cold-partitioning-in-… * Got SPEC running locally and I think I have reproduced Ramana's failures. == Next Week == * Bank Holiday on Monday * Investiagte SPEC failures in Hot/Cold PGO * Get symbol_ref benchmarking going properly == Future == * Look at Cards for Vectorization, PGO and LTO with Michael. -- Matthew Gretton-Dann Linaro Toolchain Working Group matthew.gretton-dann(a)linaro.org

12 years, 10 months

Testing builds via cbuild

by Michael Hope

(cc'd to linaro-toolchain to archive) Hi Matt. I've had a look at the manual builds you tried to spawn. Here's what I did to run cbuild locally to test it: * cd linaro * bzr branch lp:cbuild * cd cbuild/slaves * cp -a example `hostname` * cd `hostname` * make -f ../../lib/build.mk final/gcc-4.8+svn190558.stamp I'm not proud of the whole 'slaves/$hostname' setup, but it is what it is. Results are in $version, such as gcc-4.8+svn190558. The build tree is in $version/gcc/default/build. Nuke using rm -rf final results $version. See lib/common.mk and override the email address etc in local.mk to stop build results going out You should put a proxy in $http_proxy or ~/.wgetrc to reduce the download cost. Please add to the cbuild README. A nit: we use the Debian versioning scheme so the version should be 4.8~svn190558, i.e. a SVN checkout leading up to 4.8. Compare with 4.7+svn1234, which is a SVN checkout of the 4.7 branch. The tarballs look generally good. I've spawned them into the a9hf queue as that's what we benchmark on. Note that they're low priority due to not having 'linaro' in the name. -- Michael

12 years, 10 months

Function alignment and benchmark results

by Michael Hope

Zhenqiang's been working on the later split 2 patch which causes more constants to be built using a movw/movt instead of a constant pool load. There was an unexpected ~10 % regression in one benchmark which seems to be due to function alignment. I think we've tracked down the reason but not the action. Compared to the baseline, the split2 branch took 113 % of the time to run, i.e. 13 % longer. Adding an explicit 16 byte alignment to the function changed this to 97 % of the time, i.e. 3 % faster. The reason Zhenqiang and I got different results was the build-id. He used the binary build scripts to make the cross compiler, which turn on the build ID, which added an extra 20 bytes ahead of .text, which happened to align the function to 16 bytes. cbuild doesn't use the build-id (although it should) which happened to align the function to an 8 byte boundary. The disassembly is identical so I assume the regression is cache or fast loop related. I'm not sure what to do, so let's talk about this at the next performance call. -- Michael

12 years, 10 months

Actions from Toolchain Performance Call 21 August 2012

by Matthew Gretton-Dann

All, I have updated the minutes from today's Performance Call here: https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2012-08-21 The following are the actions from the meeting: * michaelh to folow-up and ping Mans on getting a hold of his benchmark runs * michaelh to investigate regression with movw/movt patch by hand * mgrettondann to run current symbol ref splitting patch over SPEC against FSF trunk * michaelh to point mgrettondann to existing cards * michaelh and mgrettondann to start writing card for PGO work * mgrettondann to pick up Hot/Cold Partitioning patch from ramana, cross-test against SPEC for correctness, and then do a benchmarking run * ramana to create a Blueprint for min-idion in middle-end and update Todo list with link * mgrettondann to update todo list with changes in 2012.08 release. * zchen to work on shrink-wrapping * clyon to update his vext patch The next meeting is on 4 September and a proposed Agenda is here: https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2012-09-04 Please add any items you wish to discuss to the agenda. Thanks, Matt -- Matthew Gretton-Dann Linaro Toolchain Working Group matthew.gretton-dann(a)linaro.org

12 years, 10 months

Re: [Linaro-toolchain-builds] [cbuild] eglibc-2.16~svn20181 armv7l failed

by Michael Hope

On 18 August 2012 12:06, Ramana Radhakrishnan <ramana.radhakrishnan(a)linaro.org> wrote: > This should have been fixed by this patch . I'm a bit surprised that > we are seeing these failures still ? > > ../ports/sysdeps/unix/sysv/linux/arm/ldsodefs.h:41:0: warning: > "MORE_ELF_HEADER_DATA" redefined [enabled by default] > > http://permalink.gmane.org/gmane.comp.lib.glibc.ports/1428 > > which should have made it back to eglibc 2.16 ? Well, that's embarrassing. The eglibc script is used to both build eglibc and to use a fixed eglibc to test GCC. The latter was winning so every snapshot build was actually building eglibc 2.12. Fixed and testing, -- Michael

12 years, 10 months

[ACTIVITY] report week 33

by Peter Maydell

Current Milestones: || || Planned || Estimate || Actual || ||cp15-rework || 2012-01-06 || 2012-06-23 || 2012-06-24 || ||a15-lpae-support || 2012-07-13 || 2012-07-20 || 2012-07-20 || ||clean-up-kvm-patches || || || || ||track-kvm-abi-changes || || || || ||fake-trustzone || || || || == clean-up-kvm-patches == * started on driving "read/write cp15 regs from kernel" from the existing QEMU hashtable of cp regs it knows about. First cut seems to work, but needs more testing and also qemu's ARMCPRegInfo struct needs to provide raw_read/write methods which bypass access permission and similar checks. == other == * shepherded various things into upstream QEMU for 1.2 release freeze: arm-devs patch queue, linux-user patches, some minor stuff * qemu-linaro 2012.08 released * travel booked for Connect/ELC-E/KVM Forum; rest is blocked on the Connect conference hotel discount rate/booking info appearing KVM blueprint progress tracker: http://apus.seabright.co.nz/helpers/backlog?group_by=topic&colour_by=state&… -- PMM

12 years, 10 months

[ANNOUNCE] Linaro GCC 4.7 and 4.6 2012.08 released

by Michael Hope

The Linaro Toolchain Working Group is pleased to announce the 2012.08 release of both Linaro GCC 4.7 and Linaro GCC 4.6. Linaro GCC 4.7 2012.08 is the fifth release in the 4.7 series. Based off the latest GCC 4.7.1+svn189992 release, it includes many ARM-focused performance improvements and bug fixes. Interesting changes include: * Updates to GCC 4.7.1+svn189992 * An ABI fix for vectors with the wrong layout * Backports improvements to the NEON vdup instruction with immediates * Backports a fix to performance regressions in partial redundancy elimination at high optimisation * Backports faster 64 bit core register adds with immediates A bug has been fixed in GCC's implementation of the AAPCS rules for the layout of vectors that could lead to wrong code being generated. Vectors larger than 8 bytes in size are now by default aligned to an 8-byte boundary. This is an ABI change: code that makes explicit use of vector types may be incompatible with binary objects built with older versions of GCC. Auto-vectorized code is not affected by this change. Fixes: * LP: #1020601 Strange behaviour with __builtin_unreachable() * PR38785 huge performance regression on EEMBC bitmnp01 * PR53447 missed optimization of 64bit ALU operation with small constant Linaro GCC 4.6 2012.08 is the eighteenth release in the 4.6 series. Based off the latest GCC 4.6.3+svn189991 release, this is the fifth release after entering maintenance. Interesting changes include: * Updates to 4.6.3+svn189991 * An ABI fix for vectors with the wrong layout The source tarballs are available from: https://launchpad.net/gcc-linaro/+milestone/4.7-2012.08 https://launchpad.net/gcc-linaro/+milestone/4.6-2012.08 Downloads are available from the Linaro GCC page on Launchpad: https://launchpad.net/gcc-linaro More information on the features and issues are available from the release page: https://launchpad.net/gcc-linaro/4.7/4.7-2012.08 Mailing list: http://lists.linaro.org/mailman/listinfo/linaro-toolchain Bugs: https://bugs.launchpad.net/gcc-linaro/ Questions? https://ask.linaro.org/ Interested in commercial support? Inquire at support(a)linaro.org -- Michael

12 years, 10 months

[ACTIVITY] Aug 13-Aug 17

by Christophe Lyon

== Progress == * Out of office Friday 17 * Attended Virtual Connect sessions: * Vectorization * PGO/LTO: provided benchmarking results on Webkit computed in ST last year. * At last managed to have bzr working * Prepared a patch for "constant vec permute operation for the vext instruction" blue-print, based on linaro-gcc/4.7 * Some pending internal work == Next week == * Out of office Monday 20 * Check reviews for my patch to have it accepted.

12 years, 10 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain