All,
During Connect the suggestion was made that each working group should have
its own IRC Channel for discussions and topics relating to the group in
particular (as opposed to #linaro which is 'generic' Linaro conversations).
Therefore I have just set up #linaro-tcwg on Freenode for the Toolchain
Working Group.
This channel is public and open to anyone who wants to talk with the TCWG
group about anything toolchain related.
Thanks,
Matt
--
Matthew Gretton-Dann
Toolchain Working Group, Linaro
The Linaro Toolchain and Platform Working Groups are pleased to
announce the 2013.07 release of the Linaro Toolchain Binaries, a
pre-built version of Linaro GCC and Linaro GDB that runs on generic
Linux or Windows and targets the glibc Linaro Evaluation Build.
Uses include:
* Cross compiling ARM applications from your laptop
* Remote debugging
* Build the Linux kernel for your board
What's included:
* Linaro GCC 4.8 2013.07-1
* Linaro Newlib 2.0 2013.06
* Linaro Binutils 2.23 2013.06
* Linaro Eglibc 2.17-2013.07-2
* Linaro GDB 7.6 2013.05
* A statically linked gdbserver
* A system root
* Manuals under share/doc/
The system root contains the basic header files and libraries to link
your programs against.
Interesting changes include:
* The sysroot is based on Linaro versions of Eglibc. About details of
Linaro Eglibc, please refer
https://releases.linaro.org/13.07/components/toolchain/eglibc-linaro.
The Linux version is supported on Ubuntu 10.04.3 and 12.04, Debian
6.0.2, Fedora 16, openSUSE 12.1, Red Hat Enterprise Linux Workstation
5.7 and later, and should run on any Linux Standard Base 3.0
compatible distribution. Please see the README about running on x86_64
hosts.
The Windows version is supported on Windows XP Pro SP3, Windows Vista
Business SP2, and Windows 7 Pro SP1.
The binaries and build scripts are available from:
https://launchpad.net/linaro-toolchain-binaries/trunk/2013.07
Need help? Ask a question on https://ask.linaro.org/
Already on Launchpad? Submit a bug at
https://bugs.launchpad.net/linaro-toolchain-binaries
On IRC? See us on #linaro on Freenode.
Other ways that you can contact us or get involved are listed at
https://wiki.linaro.org/GettingInvolved.
Know issues:
* Some version information in README are incorrect.
* gdb can not backtrace into libc.
Notes:
* To use all of the features of Linaro eglibc, the sysroot in 32-bit
toolchain release is updated to Linaro eglibc, which is 2.17. If you
get runtime errors about libc version, please get the sysroot from the
release tarball
(gcc-linaro-arm-linux-gnueabihf-4.8-2013.07-1_linux/arm-linux-gnueabihf/libc/)
or download from launchpad
https://launchpad.net/linaro-toolchain-binaries/support/01/+download/linaro…
If you do not want to use Linaro sysroot, you'd add option to gcc to
find your sysroot:
--sysroot=<directory>
* To run 32-bit application built from arm-linux-gnueabihf toolchain
in aarch64 system, you'd copy sysroot and runtime from release package
to your root of aarch64 system. i,e.
scp -r gcc-linaro-arm-linux-gnueabihf-4.8-2013.07-1_linux/arm-linux-gnueabihf/libc/*
AARCH64-SYSTEM:/
scp -r gcc-linaro-arm-linux-gnueabihf-4.8-2013.07-1_runtime/* AARCH64-SYSTEM:/
Hi,
We've noticed an issue trying to use the Linaro AArch64 binary bare metal
toolchain release with the MMU turned off for some low-level tests.
Anytime puts, sprintf, etc. gets called, a reent structure gets created with
references to STDIN, STDOUT, STDERR FILE types. A member in the __sFile
struct, _mbstate, is an 8 byte struct, but is not aligned on an 8 byte
boundary. This means that when memset (or a similar function) gets called on
this struct, and doesn't operate one byte at a time, a data alignment fault
will be generated when operating out of device memory, such as on a system
where the MMU has not yet been turned on yet.
I'm still examining possible fixes (I'll probably look at building with
-mstrict-align first), but I wanted to check if anyone had thoughts on the
subject and if Newlib upstream or Linaro consider using Newlib with the MMU
turned off to be a valid use case or if running the code that turns on the MMU
is considered a prerequisite to everything else.
Thanks,
Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
== Progress ==
* Buildbots
- Work-around for ClamAV (r195646), new bot in!
- http://lab.llvm.org:8011/buildslaves/linaro-chrome-03
- After a week stable, I'll deactivate the old chromebook and re-fit it
- Looking at MCJIT random breakages on A15 self-hosting tests
- http://llvm.org/PR18057
- Proposed a fix, http://llvm-reviews.chandlerc.com/D2287
- Installed Arch on the ODroid XU, running a local buildbot on it
- Investigating llvm-rtdyld but in reading debug information
- http://llvm.org/PR18085
* Vectorizer
- Mapping, discussing and proposing implementation for pragmas
- http://llvm.org/PR18086
- http://llvm-reviews.chandlerc.com/D2289
* Release 3.4 RC1
- Running benchmarks comparing 3.3 with 3.4
- EEMBC within noise levels for geomean
- O3: ~0.2% faster, ~0.7% bigger
- Os: ~1.3% slower, ~0.6% bigger
- Phoronix, ImageMagick: OK within std dev
* LLVMAndroid
- Tinti compiled the kernel 3.4 and some libs with LLVM
- Trying to put Android on the ODroid XU (the official one is quite poor)
- XU redirected to set as a buildbot, once ready, I'll use the other
for Android
* Background
- Lots of patch reviews, discussions
- Helping Graphics WG with Clover
== Issues ==
Still ill because of implant, on/off throughout the week.
== Plan ==
* Put the self-hosting bot up once it's fixed
* Fix the XU bot
* Try LLVM Android on XU again
* Continue with the simple vectorization pragmas
* Waiting on benchmark test-suite mode to create a new benchmark test-suite
== Progress ==
* lib/git-parser.sh: Add support for ~ as branch designator and
multi-/ branches.
* Refactor cbuild2 to use git parser
* Created stamp functions for cbuild2
US Thanksgiving Holiday
== Next ==
* Finish refactor of cbuild2 to use git parser.
* Create unified parser that wraps git parser.
* Finish refactor of cbuild2 to use stamp functions.
== Issues ==
* None
Forgot to hit send on this one
== Progress ==
* Add documentation for git-parser.sh.
* lib/git-parser.sh: Add no-url support.
* testsuite/test.sh fix invocation of testsuite/git-parser-tests.sh
to include ${topdir}.
* Add lib/git-parser.sh and testsuite/git-parser-tests.sh.
* Fix corner cases with <user>@<url>/<repo>.git[/branch]@<revision>
1) Allow http urls to be processed by 'git' cases.
2) Error check git-new-workdir and git checkout
3) Parse revision and branch properly when there might be a <user>@
in the url.
* testsuite/test.sh: Update for breath to cover
user@<url>/<repo>.git@<revision>
* Fix get_srcdir to work with <user>@<repo>.git/branch@revision
* Fix get_toolname and get_srcdir when using <user>@<repo>.git@revision
== Issues ==
* None
== Next ==
* Have cbuild2 start using the git parser
== Issues ==
* Still some cbuild oddities.
== Progress ==
* LRA on AArch32:
o TCWG-342 : UPSTREAM: LRA issue in gfortran with store minmaxsi
- Performance validation is OK, confirmed by kyrill.
- Waiting for approval.
o TCWG-344 : UPSTREAM: Thumb bootstrap failure with LRA
- Pinged for THUMB_SECONDARY_INPUT_RELOAD_CLASS patch review
- Validate and post patch for PR58785:
http://gcc.gnu.org/ml/gcc-patches/2013-11/msg02459.html
o TCWG-345 : Analyse performance of LRA for ARM
- Analysing results mismatch between 2 pandas
- Configured and ran spec2000 on Chromebook
- Analysis ongoing
== Next ==
* Continue on LRA
* Reviews
== Progress ==
* Released GCC 4.7 and 4.8 2013.11 releases.
* Investigated potential regressions on trunk, as reported by
continuous cross-validation.
Reported some cases to Kyryll. Another, reported to Bin, turns out
to be an unrelated, unstable testcase recently introduced.
Will have to give a closer look at big-endian tests.
* Updated libsanitizer patch for AArch64. It builds again but is not
functional yet (running in the Foundation model currently); getting
support from libsanitizer developers. Support for AArch64 will have to
be committed in LLVM, and merged into GCC later. I'm going to continue
prototyping under GCC though, and will submit changes to the
libsanitizer team when ready.
* GNU tar regression (extended_negsidi pattern): posted bugzilla,
fixed by Richard.
* cbuildv2: gave another try, pointing to staging.g.l.o, to discover
that it was outdated too. Rob has fixed it since then.
* Backports: gave some support to Michael Collison to help him get to speed.
Prepared backport of Zhenqiang's "enhance phiopt
to handle BIT_AND_EXPR" (TCWG -303)
== Next ==
* Resume "disable-peeling" work. Mostly check that the current trunk
contains what we want.
* cbuildv2: retry to create source release 2013.11
* Backports: commit TCWG-303, and Charles' backport of his testsuite fix
look at the others in the list.
* libsanitizer for AArch64: make it functional
== Progress ==
* GDB ARM Process Record:
- Completed work on arm process record Advance SIMD, vfp and coprocessor
instruction recording.
- Submitted initial patch for SIMD. VFP and coprocessor instruction
decoding.
- Resubmitted previous patches after incorporating suggestions.
- Resolved patch line wrap issues and formating issues.
* Macau visa and travel planning
* Got started with using concur
== Plan ==
* GDB ARM Process Record:
- Follow up on previous patches.
- Test VFP, SIMD and other advance instruction types recording.
- Fix issues and submit their fixes if any.
* Run GDB testsuite in various configurations and analyze failures.
