== Progress ==
* spec2k comparison between ARM and x86
- Trying to reproduce some of the earlier optimization studies
- Set up Acovea Trying milepost gcc
* VRP based zero/sign extension elimination
- Posted the modified patch
== Plan ==
* Continue with spec2k comparison between ARM and x86
* Wiki Cleanup
== Progress ==
* Made it back from the Tetons after a rainy climbing trip
* Helped Vish with #357
* Cbuildv2 improvements for cross builds and binary releases
* Wrote script to for better Jenkins support
* Added more user parameters to Jenkins config page for building
toolchains.
== Plans ==
* More work on Cbuildv2 for building binary releases
* Write more Cbuildv2 docs
* More help on #357
* Start going through Wiki pages
* Investigate lava-tool so Cbuildv2 can use Jenkins slaves remotely
== Progress ==
* Short week (3 days off to move house)
* Submitted outstanding glibc patches after 2.18 release
* Wrote some glibc allocator tests which have exposed some minor issues
== Issues ==
* None
== Plan ==
* Complete glibc allocator tests and submit them
* Get malloc implementation functionally complete
--
Will Newton
Toolchain Working Group, Linaro
== Progress ==
* 2013.08 4.8 release:
- completed achievable backports (postponed some with problems to
next release)
- created & uploaded release. Will be announced next week along with 4.7
- Matthias a reported a problem in c++/java
* Aarch64 frame layout: submitted sample code for internal discussion.
* Wiki cleanup: started
* trunk validation:
- continued to work on internal validation of trunk using our
compute farm (build+cross validation) to help catch regressions early.
- validating every commit seems too heavy currently
== Plan ==
next week off
== Progress ==
* Connect / LLVM Meeting
- Checking times, booking tickets, etc
* Divmod
- Some more divmod work, SelectionDAG changed enough to break my merge
- Since it's only 64-bit support, we'll postpone implementation for a
later date
- Internal discussions with ARM, trying to approach it in a different way
* Buildbots
- Investigating MCJIT test failure in buildbot
- Some other random breakages
- Testing an ODroid U2 as a buildbot, will leave it running for a week
non-stop
- Checking why ClamAV has different output on Chromebook vs.
ODroid/Panda/x86
* ODroid U2
- Testing ODroid vs. Chromebook / SDCard vs. External HD
- ODroid with SDCard is faster than Chromebook with External HD!
- The huge heat-sink, the possibility of adding a fan and its form factor
make it a really good candidate for a buildbot
* Background
- Meetings with ARM, LLVMLinux
- Interviewing potential candidates
- Reviewing & committing patches, discussions, etc.
* Cross-compilation
- Preparing the terrain to start investigation
== Plan ==
Another week off! :D
Progress:
* v7 mach-virt upstreaming:
** sent out an RFC patchset implementing '-cpu host' for QEMU for v7 CPUs
* QEMU maintenance:
** versatile-pb PCI issues came up again; testing kernel patches etc
-- PMM
Is there a way to generate A32 code with the gcc-linaro-aarch64- compilers? I looked at the bare metal and linux 2013.07 versions, but didn't see a way to do this.
Also, the compiler doesn't complain about -mcpu=cortex-a53 or -mcpu=cortex-a57, but I get unknown cpu errors from the assembler for these options. It looks like it is the case today that there is just generic v8 code generation and more specialized code generation will come later. Is that right?
Thanks, Don
== Issues ==
* None
== Progress ==
* Investigate and close lp:1208945 and lp:1210713.
- For lp:1208945, libc.so.6 should be at /lib/arm-linux-gnueabihf.
- For lp:1210713, aufs is not a part of standard linux kernel release.
But aufs is supported by Ubuntu release. So maybe need it for future
releases.
* Conditional compare
- Enhance reassoc pass to handle conditional compare
- Investigating bootstrap issue when expanding conditional compare to
optimized RTL.
* Investigate LDTS tickets about multilib build issues.
- Local builds are OK for Linaro GCC 4.7 and 4.8.
== Plan ==
* Send out the conditional compare patches for review.
== Panned leaves ==
* Aug. 19-20: annual leaves
* Sept. 3-5: internal meeting.
Folks,
This week I acquired an ODroid U2, which is an Exynos4 (quad-core A9 at
1.7GHz each), 2GB RAM, and a massive heat-sink (which even has power supply
for a fan).
I ran some ball-park compilation time benchmarks, comparing to the
Chromebook, and the results are interesting. The ODroid with an SDCard
(32GB Sandisk Ultra HC-1) is faster than the Chromebook with an external
USB 3.0 / SATA hard-drive.
LLVM Build Times (min)ChromebookODroidODroid-USBBuild1008180Check-all545
Test-suite424038
The test-suite and check-all results are statistically equivalent, but the
build time is better because of the number of CPUs, but not twice better.
Disk is more of an issue on the test-suite, which can be clearly seen above
(-j2 for Chromebook, -j4 for ODroid, but same time).
My USB stick is not the best, so that doesn't mean much. Also, I can't get
the ODroid to even recognize the SATA disk when I plug in because of the
power it needs. So, we'll have to do with those numbers. I'm using the
ODroid Ubuntu image (based on 13.04), which worked out of the box (except
the SATA disk and HDMI).
I'll let the board run for a week at home (room temperature ~ 25C) as a
buildbot, with the fan on all the time and see if it copes with constant
load for such a long time. Pandas couldn't do that, Chromebooks can.
Since the ODroid U2 is a dev board, which has a small form-factor, can be
turned on/off remotely and won't sleep when the lid is closed, has a decent
Ethernet port (Chromebook's wired adapters are *horrible*, and having
dozens of Wireless clients in the lab is just not possible), and don't have
the risk of being turned off by someone else, like the Calxedas, I'd say
that it might end up as the best buildbot yet. (The new XU is an Exynos5
octo-core monster, might be even better).
After the initial week load test, if all goes well, I want to bootstrap GCC
and run some tests on it, so I'll be calling for volunteers to help me.
cheers,
--renato
== Progress ==
* 2013.08 4.8 release:
-- merged many backports
- sorted a few dependencies problems between patches
- spawned all intermediate jobs (ie merge commits) to make sure
there was no regression
* 2013.08 4.7 release:
- made a trial branch merge to confirm that all builds succeed
(Matthias reported a build failure for aarch64)
* trunk validation:
- continued to work on internal validation of trunk using our
compute farm (build+cross validation) to help catch regressions early.
== Plan ==
* 2013.08 4.8 release:
- final backports
- actual release
* Resume work on aarch64 frame layout.
* Resume work on disabling peeling.
