== 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.
ABE benchmarking automation - TCWG-360 [6/10]
* Fixed an awkward escaped process
* Struggled with LAVA timeouts & discovered that some Junos
accidentally have a baked-in timeout
* More discussion/thinking about where to store benchmark source
* Some trouble with intermittent flakiness when copying large chunks
of data over the lab network
Investigating cache effects on Juno - LDTS-1238 [2/10]
Misc - [2/10]
* Featuring catomics (TCWG-436) - implemented a few missing catomics
(well under 1/10)
=Plan=
Pack for office move
Fix intermittent copying problem
Look more at cache effects on Juno
Test Jenkins dispatch (Rob says it works now)
* Look into triggering coremark on every backport
Carry on, hopefully close, storage discussion
Benchmark catomic patches
Write up/think about where to go with libm exercising
== Progress ==
* Automation Framework (CARD-1378 2/10)
- Rebooting machines, again...
- Fiddling with bugzilla, wiki
* Release 3.6 (TCWG-575 5/10)
- Investigating ARMv7 bootstrapping failures
- Rebuilding manually with cmake, as autoconf build is bogus
- Turns out wasn't autoconf, but a NEON bug reported 14th Dec
- Benchmarking AArch64 3.6-RC1 against 3.5.1 - all good
* Background (3/10)
- Code review, meetings, discussions, etc.
- More Jira farming
- Investigating some weird llvm-objdump issues
- Fixing ninja output issue on bots with an ugly hack
== Plan ==
* Bisect NEON bug, revert the patch, back-port to 4.6 RC2
* Add a NEON+T2 full buildbot (dragonboard) to the list of public bots
* Benchmark ARMv7 3.6 RC1 or RC2 against 3.5.1
== Progress ==
* GCC trunk/4.9 monitoring (1/10)
* AArch64 sanitizers (3/10)
- patched LLVM to reduce the number of failures to 2 on Juno
- need access to a board with different memory layout to make sure
my patches actually support all configurations
* Neon intrinsics tests (2/10)
- committed most of the series
- addressed comments received on a few of them
- looked at error reported by vmax test: I needed to force AArch64
FPCR.DN=1 in the test, posted updated patch.
* Misc (4/10)
- meetings, conf-calls, emails, ...
== Next ==
* GCC trunk/4.9 monitoring
* AArch64 sanitizers
* abe: look at backport and tcwgweb scripts
