== Progress ==
* GCC trunk cross-validation
- reported a few regressions
* Automation Framework (2/10)
- looked at Jenkins configuration & logs of some failures
* AArch64 libsanitizer (1/10)
- tried to use cbuild2 in the lab to build & test on HW, but all my
build attempts failed for various reasons
* Neon intrinsics tests (3/10)
- feedback from upstream requests some renaming changes + GNU coding
style fixes
- since reformating the existing testsuite is a manual and
error-prone task, it will bring additional delay in improving GCC
testsuite.
- it's probably more efficient to run the existing tests regularly
and start reporting & fixing the bugs identified, not waiting for the
full conversion
- updated the existing tests for fp16 and poly* types support with
GCC (reference built with armcc)
- interestingly, compiling the original testcases with armcc for
aarch64 caused ICE on 28 source files.
* Misc (meetings, conf-calls, ....) (4/10)
== Next ==
Holidays for 2 weeks
== Progress ==
* Monday holiday
* Automation Framework (CARD-1378 6/8)
- TCWG D01 moved in, Chromebooks out
- Movng LLVM buildbots to D01s
- D01s have no NEON support... :S
- We might have to move some Chromes back in
- Moving hackboxes to Chromebook 2s
* Background (2/8)
- Code review, meetings, discussions, etc.
== Plan ==
* Deal with NEON issue in the rack
* Finish Cauldron presentation
* Try to get the D01s as buildbots, even without NEON
== Progress ==
* AArch64 GDB reverse watchpoints issue. [TCWG-503] [4/10]
-- Found a new fix in generic process record implementation.
Testing stalled by too many 2500 failures seen on arm-linux-gdb in
general and some 850 record/replay implementation.
* AArch64 GDB handling of functions with empty prologue. [TCWG-504] [4/10]
-- Analysis of prologue generated by aarch64-gcc
-- Make an understanding of code implementation for arm-linux-gdb.
-- Try to reproduce reported bugs.
* Testing and Analysis of testsuite failures in arm-linux-gdb [TCWG-509] [1/10]
* Browsing gdb related upstream discussions. [1/10]
== Plan ==
* AArch64 GDB reverse watchpoints issue. [TCWG-503]
-- Test and submit fix for target record for the case where we cant
step breakpoints.
* Investigate issues in arm-linux-gdb testsuite results. [TCWG-509]
* Travel preparations to UK for Tools cauldron and TCWG sprint.
-- Obtain health certificate for international travelers.
* On Holiday from 14th to 17th July 2014.
=Progress=
memcpy regression on A9 - TCWG-390 [7/10]
* Tweaked bench.py some more
* Cobbled together a bare metal version of cortex-strings benchmark
* Was surprised to find that the problem does not relate to Linux
* Have some evidence that points at the branch predictor
Meetings/mail/etc [3/10]
=Plan=
See if A9 performance is recoverable without sacrificing other targets
Push some of my improvements into the cortex-strings repo
Possibly write up my cortex-strings-benchmarking-in-lava method
Back to cbuild benchmark automation
== Progress ==
Zero/sign extension elimination (TCWG-291) 10/10
- Patch updated based on review comments.
- Regression tested with standard set-up
- Created test-cases.
- Set-up additional architectures for validation
* aarch64-none-elf --with-abi=ilp32 (Foundation model)
* aarch64-none-linux-gnu --with-abi=ilp32 seems to be broken.
* Set-up qemu based s390x-ibm-linux
* Tried x86_64-linux -mx32 but ran into many issues.
- Patch now waiting for s390x-ibm-linux. All others are OK.
- will post once the results are available
== Plan ==.
- Spec2k regressions
- sha1 regressions
- 8th and 9th on holiday.
== This week ==
Provide ldp/stp peephole optimization for Aarch64 [TCWG-446] [6/10]
- Investigated options for improving ldp/stp pairing and developed
patch
- Testing underway
Launchpad 1267761 - miscompilation of unsigned comparison on aarch64 [1/10]
- Backported revision 206529 from trunk
- Testing under way on Jenkins
Launchpad 1296942 - marked fixed released based on backport by Yvan Roux
[1/10]
- July 4th holiday [2/10]
== Next week ==
Complete testing on Launchpad 1267761 and TCWG-446 and initiate code review
== Future ==
Travel to Cambridge on July 11th for Cauldron and TCWG Spring
Am 05.07.2014 17:36, schrieb Emilio Pozuelo Monfort:
> Control: reassign -1 gcc4.8,gcc4.9
>
> Hi,
>
> This is still a problem with GCC 4.9. Is there any progress on this? This is
> making aegisub FTBFS on armel, blocking the libass transition.
afaik, no. See also https://gcc.gnu.org/ml/gcc/2014-07/msg00000.html
