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
Hi,
We've noticed that in the 14.11 toolchain binary release that the .asc files
contain md5sums instead of PGP signatures. Would it be possible to either
switch these files to contain signatures or change the filename to indicate
that they contain md5sums?
I also noticed that an md5sum is missing:
http://releases.linaro.org/14.11/components/toolchain/binaries/armeb-linux-…
Finally, there appears to be some inconsistent usage of tuples in the download
directories. Would it be possible to use the same tuple for a particular
toolchain everywhere that tuple is used? For example, for the arm-none-eabi
toolchain, the directory is "arm-none-eabi", but the compiler tarball has only
"arm-eabi".
Thanks,
Chris
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
== Progress ==
* Automation Framework (CARD-1378 1/10)
- Setting up new box
* Release 3.6 (CARD-1431 5/10)
- Looking for the patch that introduced a major NEON regression since December
* Background (4/10)
- Code review, meetings, discussions, etc.
- More Jira farming...
- Some EuroLLVM paper reviews
- LLVM/Android planning
== Plan ==
* Keep trying to find the bug in release 3.6
* Try to have some time to fix the NEON unwinder issue
* Preparing for Connect
== Issues ==
I cocked up the LLVM 3.6 ARM release last December when I
inadvertently ignored a bug report about clang not self-hosting on
NEON machines. To make matters worse, I was the one that decided to
move *all* our buildbots to non-NEON machines, expecting that the
test-suite on a Chromebook would catch all NEON problems.
There are limits to human intelligence, not human stupidity.
== Progress ==
* LLD (1/10, TCWG-561, TCWG-563, TCWG-570)
- Updated and added more cards, adding more detail and loose priorities
- Rebased, fixed up and resubmitted relocation test patch
* AArch64 ILP32 toolchain (4/10)
- Attempted various SPEC2k runs and fixed issues found
* Submitted patch for AArch64 -Bsymbolic ld issue (1/10)
* Connect slides (2/10)
* Other stuff (1/10)
- Email, meetings, etc.
* Tuesday looking after sick child
== Issues ==
* Juno access has been patchy
== Plan ==
* Get SPEC2k running ok on Juno and with ILP32
* Push remaining LLD patches
--
Will Newton
Toolchain Working Group, Linaro
Hello,
I have a question about the status of overo support in qemu-linaro vs upstream qemu; from a quick look on the Git commits for qemu-linaro, most things seemed to have been ported back upstream into qemu as of v2.0.0, although there does appear to be some recent new commits. However, I'm looking for overo board support, and although I see that OMAP3 chip support has been merged upstream, there aren't any board configuration files for overo. What would be the easiest way to get working qemu overo board support?
Additionally, I don't see any recent binary packages available for qemu-linaro. The qemu-linaro packages on the Ubuntu PPA haven't been built for almost a year now, and the releases.linaro.org page doesn't seem to have recent qemu-linaro builds either.
Thanks,
Dominic
* TSAN support for Aarch64 (5/10)
Up streamed make file changes for building non x86_targets (TCWG-579).
Working on memory map layout for TSAN in Aarch64 (TCWG-581) .
* Fix Bug 863(Linaro)/ 63949(FSF) (2/10).
Tested patches and fixed few aarch64 regressions.
got feedback that approach is good. planning to send a revised patch
for stage 1.
* Emails, meetings. (3/10)
* 1-1 with maxim,christophe,Ryan, linaro status call.
* internal AMD meetings, 1-1 with AMD manager.
* GCC mailing list.
Leave on 26-Jan-2014 (India Holiday)
== Plan ==
* TSAN support for Aarch64 work on memory layout.
* Send revised patch for Bug 863
== Progress ==
LLDB vs GDB investigation [TCWG-583] [4/10]
-- Scoring of previous patches and mailing list discussions
-- Tried and was able to build+test lldb on x86_64 linux
-- Tried and was able to build (but not test) lldb on arm linux
-- Tried lldb AArch64 build but couldnt get it going successfully.
Some gdb bug fixing and wrap up open gdb stuff [4/10]
Miscellaneous [2/10]
-- Meetings, Emails etc
-- Connect Preparation: Flights Confirmation, Visa pick up etc.
== Plan ==
Try fixing LLDB testsuite on arm and try out aarch64 build if possible.
