== Progress ==
* Disable-peeling:
- benchmarking locally on snowball
- failed to build reference branch on cbuild, for an unknown reason
* Turnoff 64bits ops in Neon:
- committed upstream in 4.9 (now stage 1)
- benches of backport into Linaro-4.7 OK: no significant diff,
except +12.6% on spec2k's crafty)
- Filed merge request.
* Vectorizer cost model:
- benches of backport inot Linaro-4.7 OK (no significant diff, as expected).
- Filed merge request.
* Revert-coalesce:
- benches ran in cbuild, but no *-diff.txt file generated.
* Libsanitizer:
- testsuite results OK. All unsupported tests are normal.
* Neon intrinsics codegen:
- got internal feedback
* GDB reverse debug:
- filed 2 bug reports after internal requests.
* Misc:
- filed several bug reports against cbuild to track the problems I observed.
== Next ==
* Disable-peeling:
- analyze bench results
- understand/'fix what's wrong with cbuild
* Turnoff 64bits ops in Neon:
- backport to Linaro-4.8
* Revert-coalesce:
- manually compute bench differences if unable to have cbuild do it.
* Libsanitizer:
- propose patch upstream.
== Progress ==
Knocked out more GDB remote configuration failures that were failing due to
timeouts.
Had 1:1 with Matt for direction on GDB improvement plan.
Looked around for Ireland visa process and filled out visa application.
== Plan ==
Complete review of remote timeout based test case failures.
Start work on the GDB improvement blueprint in JIRA from this week.
Get remaining documentation for Ireland visa and complete application.
== Progress ==
- Looking at TLS relocs and coming up with test cases for garbage
collecting them.
- Patch for missedout testcases in gc section is up streamed. Thanks to Marcus.
== Plan ==
- Complete gc section test cases for TLS relocs.
- Understand and evaluate gprof support work for Aarch64
Misc
-----
Leave on Wednesday and Thursday (27th and 28th)
== Progress ==
- Worked on VRP based zero/sign extension elimination at tree level
- Some regression test cases are failing; investigating them
== Plan ==
- Analyse the reason for test case failure and fix them
- Extend the code to handle all the possible cases (currently
implemented for subset to get the framework working)
== Issues ==
* None
== Progress ==
* Libunwind AArch64 support:
- basic implementation for building lib and testsuite done
- but even a simple test case doesn't work for the moment
== Plan ==
* Libunwind AArch64 support:
- continue AArch64 specific implementation and informtation gathering
== Progress ==
* EuroLLVM paper review
* Disabled EH tests on ARM for now
* Fixed TSVC: NEON vs. VFP VMUL.f32 (and IEEE 754 correctness)
* Changed FeatureNEONForFP to false on EABI ARM targets unless unsafe-math
* Trying Arndale again, with u-boot patched, not good
* Broken Panda buildbots, trying to fix
== Issues ==
Got ill on Tuesday and only worked partially, if at all, the rest of the
week
Hopefully will be better next week...
== Plan ==
* Fix our panda buildbot, maybe add more
* Final try on Arndale GCC bootstrap before giving up
* Continue fixing test-suite failures (only 5 left)
Progress:
* VIRT-4 [Guest migration support for KVM]
** VIRT-51: vexpress migration:
** wrote and submitted patches for all the devices that need fixes
** tracked down a painful bug where the guest just hung on vmload
to a missing state-save for a timer device, submitted patch
** remaining work for this item is just responding to patch review
-- PMM
Hi folks,
I found an issue while fixing a test using the wrong VMUL.f32, and I'd like
to know what should be our choice on this topic that is slightly
controversial.
Basically, LLVM chooses to lower single-precision FMUL to NEON's VMUL.f32
instead of VFP's version because, on some cores (A8, A5 and Apple's Swift),
the VFP variant is really slow.
This is all cool and dandy, but NEON is not IEEE 754 compliant, so the
result is slightly different. So slightly that only one test, that was
really pushing the boundaries (ie. going below FLT_MIN) did catch it.
There are two ways we can go here:
1. Strict IEEE compatibility and *only* lower NEON's VMUL if unsafe-math is
on. This will make generic single-prec. code slower but you can always turn
unsafe-math on if you want more speed.
2. Continue using NEON for f32 by default and put a note somewhere that
people should turn this option (FeatureNEONForFP) off on A5/A8 if they
*really* care about maximum IEEE compliance.
Apple already said that for Darwin, 2 is still the option of choice. Do we
agree and ignore this issue? Or for GNU/EABI we want strict conformance by
default?
GCC uses fmuls...
cheers,
--renato
Hello,
I am having an issue with using the gcc toolchain for armv8. I am trying to
cross compile a simple program (helloworld.c) as suggested in the link :
https://wiki.linaro.org/HowTo/HelloAarch64.
But when I try executing the binary on the simulated armv8 (using
foundation model), I am getting error in GLIBC, specifically
"/lib/libc.so.6: version `GLIBC_2.16' not found" . Could you please help me
as to what could be wrong here?
Thanks,
Pavan
== Progress ==
* Analyzed Android kernel linker issue and created LP #1154165 to track it.
* Triaged remaining binutils Launchpad tickets.
* Setup my Pandaboard with Linaro 13.01 (13.02 oopses on boot) to run tests.
* binutils: Committed fix for LP #517081 (Floating-point assembly and
disassembly bugs on armel) upstream.
* binutils: Committed a fix for ARM EABI tests upstream.
* Lots of admin stuff.
== Plan ==
* Get binutils testsuite green in a native configuration (fix LP #812276).
* Investigate getting binutils testuite automated via cbuild/Lava.
* More bugs...
--
Will Newton
Toolchain Working Group, Linaro
== Progress ==
Reviewing GDB tests that FAIL due to timeout problems in remote
configuration.
Made some changes to some of the GDB tests that FAIL on arm targets to
check if they work by minor modifications.
Sick Days: Had been sick due to cough n fever and a drop in blood pressure
made me take most part of Thursday and Friday off.
== Plan ==
Get with Matt for Post- Connect work targets.
Review remaining GDB tests that FAIL due to timeout problems in remote
configuration.
Further experiments with GDB test suite to check support for unsupported
tests on arm.
The Linaro Toolchain and Platform Working Groups are pleased to announce
the 2013.03 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.7 2013.03
* Linaro GDB 7.5 2012.12
* 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:
* gcc updated to 4.7-2013.03:
* Updates to GCC 4.7.2+svn196272
* Includes arm/aarch64-4.7-branch up to svn revision 196225
* A fix for LP #1135633: [linaro regression] alsa-tools FTBFS with error
"unable to find a register to spill in class ‘AREG’"
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.03
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.
Short week to ...
== Progress ==
* Configured GCC testsuite to run on the Foundation model.
* Boehm GC AArch64 support:
- Submitted gc integration patch in GCC upstream for review.
- libatomic_ops AArch64 support branch re-tested and merged in mainline.
== Next ==
* AArch64 libunwind support.
== Progress ==
- Closed the blue print for gc-sections implementation since the patch
got upstreamed.
- Opened new blue print for adding more test coverage to gc-sections tests.
- Submitted a patch to enable missed out gc-sections test cases from
ld-elf group.
- Wrote gc-sections test cases for few GOT related relocs.
== Plan ==
- Understand equivalences created during CFG traversal for jump threading.
- Look at GCC code for a simple test case where jump threading is missed out.
- Continue writing gc-sections test cases for remaining relocs.
== Progress ==
- Monday was a public holiday
- Studied benchmarks and analysed the rtl/asm for redundant sign extensions
- Came up with simple test cases based on this (have 6 test cases now)
- Looked at gcc tree documentations and helper macros; tried it by
adding more debug dumps for types at tree level
== Plan ==
- Start with the algorithm for sign extension elimination
- Skipping manual changes at source level/asm level to see the
performance improvement for now.
Short week...
== Progress ==
* Catch up on internal tasks / email that piled up during holidays + Connect
* Resumed work on disable-peeling:
- local benchmarking on snowball
- restarting benchmarks via cbuild for an additional check
== Next ==
* Check benchmark results on disable-peeling
* Have a look at how to dejagnu-ize my Neon intrinsic tests
* Check results of libsanitizer branch
* Check results of 'revert-coalesce' branch
* Check bench results of '4.7-backport-vect-cost-model'
* Check bench results of '4.7-turnoff-64bits-ops'
* Investigate why cbuild did not generate all the comparisons I
expected (*-diff.txt files)
* Check whether 2013.03 release process exposed the same problems I
observed with 2013.02.
Progress (in a 1 day week...):
* qemu maintenance:
** released qemu-linaro 2013.03
** arm-devs pullreq
* VIRT-4 [Guest migration support for KVM]
** audited vexpress code for migration issues: there are a few
devices needing minor cleanup, and one (pflash_cfi01) which
has no migration support at all and needs it writing
* KVM other:
** reviewed virtio-blk refactoring patchset
-- PMM
== Progress ==
* Recuperating from Connect, catching up on email
* Attended David's and Maddog's presentation on Monday
* Investigating Arndale bug (seems to work with new kernel)
- Bootstrapping LLVM works, GCC doesn't
* Reviewing patches upstream (Mans', Tim's, others)
* Fixed three bugs on test-suite that depended on RNGs
- Only two more tests broken only in ARM
- Five others broken on both (but only visible on our bot)
- Nine EH tests that need disabling, for now
== Plan ==
* Tackle the two last ARM specific bugs
* If time allows, clear the other 5
* Try to disable any EH-specific test on ARM
* Start talks about getting an internal binary distribution process going
This is to let you know that the migration of lists.linaro.org has been
successfully completed.
As per the email I sent on Wednesday, it may take some time for the new
address of the server to be seen by your computer. You can check this by
trying to connect to the web site:
http://lists.linaro.org/
If you are able to connect and you do not get an error, this means you are
connecting to the new server and you can send email to the lists.
If you experience any problems after the weekend and you find that you
still cannot connect to the server, please reply to this email to let us
know.
Regards
Philip
IT Services Manager
Linaro
The Linaro Toolchain Working Group is pleased to announce the 2013.03
release of both Linaro GCC 4.7 and Linaro GCC 4.6.
Linaro GCC 4.7 2013.03 is the twelth release in the 4.7 series. Based
off the latest GCC 4.7.2+svn195745 release, it includes ARM-focused
performance improvements and bug fixes.
Interesting changes include:
* Updates to GCC 4.7.2+svn196272
* Includes arm/aarch64-4.7-branch up to svn revision 196225
* A fix for LP #1135633: [linaro regression] alsa-tools FTBFS with error
"unable to find a register to spill in class ‘AREG’"
Linaro GCC 4.6 2013.02 is the 25th release in the 4.6 series. Based
off the latest GCC 4.6.3+svn196247 release, this is the twelth
release after entering maintenance.
Interesting changes include:
* Updates to 4.6.3+svn196247
The source tarballs are available from:
https://launchpad.net/gcc-linaro/+milestone/4.7-2013.03https://launchpad.net/gcc-linaro/+milestone/4.6-2013.03
Downloads are available from the Linaro GCC page on Launchpad:
https://launchpad.net/gcc-linaro
More information on the features and issues are available from the
release pages:
https://launchpad.net/gcc-linaro/4.7/4.7-2013.03https://launchpad.net/gcc-linaro/4.6/4.6-2013.03
Mailing list: http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Bugs: https://bugs.launchpad.net/gcc-linaro/
Questions? https://ask.linaro.org/
Interested in commercial support? Inquire at support(a)linaro.org
--
Matthew Gretton-Dann
Toolchain Working Group, Linaro
The Linaro Toolchain Working Group is pleased to announce the release of
Linaro QEMU 2013.03.
Linaro QEMU 2013.03 is the latest release of qemu-linaro. Based off
upstream (trunk) QEMU, it includes a number of ARM-focused bug fixes
and enhancements.
This release has been updated to be based on upstream's recent 1.4.0
release. It also includes ARM KVM support patches which are in sync
with the ABI as committed to the upstream Linux kernel for 3.9.
This feature is still under development but will no longer be subject
to kernel-vs-userspace ABI breaks.
The source tarball is available at:
https://launchpad.net/qemu-linaro/+milestone/2013.03
More information on Linaro QEMU is available at:
https://launchpad.net/qemu-linaro
-- PMM
Hello
You are receiving this email because you are subscribed to one or more
mailing lists provided by the lists.linaro.org server.
IT Services are announcing planned maintenance for this server scheduled
for *Friday 15th March 2013, starting at 2pm GMT*. The purpose of the work
is to move the service to another server. There will be some disruption
during this maintenance.
In order to ensure that you do not accidentally try to use the service
while it is being moved, the current server will be shut down at 2pm.
A further email will be sent on Friday afternoon to confirm that the
migration of the service is completed. However, due to the way servers are
found, it may take a while before your computer is able to connect to the
relocated service.
After the old server has been shut down, email sent to any of the lists
will be queued, but it is possible that the sending server will still
trying to deliver the email to the old server rather than the new one when
it is started.
It is therefore *strongly* recommended that you do not send any email to an
@lists.linaro.org email address until you can connect to the new service,
which you will be able to test by trying to use a web browser to connect to
http://lists.linaro.org after you receive the email confirming that the
migration has been completed. Since the old service will be shut down, if
you are able to connect, you can be sure you have connected to the new
service.
If by Monday you are still unable to connect to the service or you are not
able to send email to an @lists.linaro.org email address, please send an
email to its(a)linaro.org.
Thank you.
Regards
Philip
IT Services Manager
Linaro
== This Week ===
* Couldnt help my luck and wasnt able to reach Hong Kong due to delay in
visa processing by Hong Kong immigration department.
* Remotely attended live streams of Linaro Connect Asia
* Tried to reproduce all open bugs under linaro-gdb project on launchpad
and created a review sheet.
* Created a comparison sheet to figure out why certain gdb tests are
failing or not being run in different configurations.
== Next week ==
* Try to enable some native only tests and see if the functionality can be
tested for remote configurations as well.
* Set out some priority on blue prints and bugs under linaro-gdb project
and start with some stuff with higher priority.
* Caught some flu over the weekend and still a bit down with fever n
headache.
