Progress
. worked on cleaning up arm config in gcc (TCWG-201)
. not really convinced I have a way to properly test the result
. a bit of bug triage
. a bit more on the 4.7 segfault bug (lp1215925)
Plans
. ping the arm*gnueabihf testsuite patch
. finish the config clean up
. revisit 4.7 segfault, now I have more suggestions from Matt
== Issues ==
* None.
== Progress ==
* Misc:
- Installed Saucy on Chromebook.
* LRA on AArch64:
- Committed RTL analyser patch.
- Committed patch which switch on LRA on AArch64.
* LRA on AArch32:
- Committed patch which fix failing assembly scan test with LRA.
- Committed LRA register notes DEAD and UNSUSED handling in LRA.
- Bootstrapped GCC with LRA on Chromebook.
- Analysis of testsuite results ongoing.
== Next ==
* Continue on LRA.
Short week (Tuesday and Wednesday went to US consulate Chennai for
VISA interview and document processing).
== Progress ==
* gprof support for aarch64
Re-based and tested. Asked permission for upstreaming in trunk.
Gibc patches are upstreamed. Thanks to Marcus.
* Aarch64 Boot strap failure.
Tried to reproduce it in V8 model. Build failing in stage 1 for me.
* 1-1 Meet with Christophe.
== Plan ==
* Back to libssp support.
* Aarch64 boot strap issue.
== Issues ==
* LTO/PGO work stopped now since libssp support priority is more.
Misc
------
October 2 India Holiday.
== Progress ==
* MPFR and GMP Build error with Latest 4.8 Release
- Reproduced MPFR error with a simplified testcase
- Found the buggy codesequence and the patch that introduced it.
- Looking at solution for this
- Reprdouced GMP error with -march=armv7-a and -mthumb
- continuing with the invetigation
* 64bit division
- Looked at current libgcc implementaion and studied the alorithm.
* Addressing patch review
- Posted second patch for zero/sign extension
* spec2k comparison between ARM and x86
- Ran spec2k with various options to validate code analysis
== Plan ==
* Continue with spec2k comparison between ARM and x86
* Continue 64bit division
* Fix GMP and MPFR build error
== Progress ==
(TCWG-270)
* Tested GDB Process Record/Replay and reverse debug feature for arm.
* Thumb32 support patch along with a couple of bug fixes made huge
improvement in testsuite results.
(TCWG-267) and (TCWG-269)
* Reviewed all previous submitted patches and wrote response patch updates.
* Implemented gdb/testsuite/gdb.dwaf2/dw2-error.exp using dwarf assembler.
(TCWG-268)
* Submitted patch for failing gdb/testsuite/gdb.dwaf2/dw2-case-insensitive.exp
(TCWG-272)
* Re-viewed and verified gdb bugs reported on launchpad and created
JIRA cards where required.
(TCWG-265)
* Generated Test data to test instruction decoding in arm specific
code of gdb process record/replay.
(TCWG-280)
* Reviewed previously submitted patches related to gdb process record
syscall support for arm targets.
* Submitted US Visa application for processing and got appointment for
Visa Interview.
* Reviewed all open JIRA cards and created new ones for future progress on GDB
== Plan ==
(TCWG-270)
* Submitt patch for bug fixes and show testsuite improvement with bug
fixes and thumb32 patch.
* Do more testing and analyse failures and try to fix them if possible.
* Verify issues reported by maintainers in old arm instruction decoding code.
(TCWG-267), (TCWG-268) and (TCWG-269)
* Update gdb/testsuite/gdb.dwaf2/dw2-error.exp as asked by gdb maintainers.
* Ping or Send response to comments.
(TCWG-280)
* Test syscall support with old patch and make changes if required.
* Travel to Islamabad on Tuesday to attend US visa interview early
morning Wednesday.
== Issues ==
* None
== Progress ==
* Update Conditional compare (CCMP) patch according to community comments.
* Investigate how to generate CCMP to support more than two compares.
- Investigate ifcombine to create more CCMP opportunities.
- Enhancing phiopt to handle CCMP case like:
if (a == 0 && b > c)
return 0
return a;
== Plan ==
* Continue on CCMP to support more than two compares.
== Panned leaves ==
* Oct. 1-7: National Day of China holiday
== Progress ==
* Profiling ImageMagick
- Clang 3.4-svn is around 10% less performing than GCC 4.7.3
- Mainly due to recursive octree-style map/reduce of most functions,
spending a lot of time
before/after branches
- Any optimization on that front won't fit the "Incubation" tag
* Profiling EEMBC
- Found 2 cases where Clang is *a lot* better than GCC 4.7.3 (pruning
bmark.c, producing much
smaller objects, and vectorizing telecom/autcor, which GCC can't)
- Most of the time, GCC is slightly better (~5% faster, ~10% smaller,
geomean)
- Wrote some scripts to run any two compilers against each other, compare
the results and
dump the ratios in a TSV file.
== Plans ==
* Update EEMBC Linaro image with Clang toolchain changes
* Look for low-hanging fruits in EEMBC
* Try comparison with GCC 4.8 and 4.9, too
* Find a way to extract Phoronix results in TSV format
== Progress ==
* Checked testsuite for glibc and gcc bootstrap on aarch64 native
* Released Linaro gdb 7.6.1 2013.09-1
* Submitted glibc pointer guard patch using TLS
* Submitted respin of pointer guard patch using a global variable
* Submitted binutils aarch64 ifunc patches for a second time
* A little bit of time on malloc
* Built office furniture!
== Issues ==
* None
== Plan ==
* Finish off pointer guard
* Hopefully back to malloc
--
Will Newton
Toolchain Working Group, Linaro
The Linaro Toolchain and Platform Working Groups are pleased to announce
the 2013.09 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.
This release introduces a set of experimental (pre-alpha) crosscompilers to
big-endian ARM architectures.
Uses include:
* Cross compiling ARM applications from your laptop
* Remote debugging
* Build the Linux kernel for your board
What's included:
* Linaro GCC 4.8 2013.09
* Linaro Newlib 2.0 2013.06
* Linaro Binutils 2.23 2013.06
* Linaro Eglibc 2.17-2013.07-2
* Linaro GDB 7.6 2013.05
* 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.8-2013.09
* Initial big-endian pre-alpha versions added
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:
http://releases.linaro.org/13.09/components/toolchain/binaries
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.
### About Linaro gdb
Linaro gdb is a release of the GNU debugger with bug fixes and
enhancements for ARM platforms. gdb allows interactive debugging of
C and C++ programs natively and remotely.
### Linaro gdb 7.6.1 2013.09-1
The Linaro Toolchain Working Group is pleased to announce the 2013.09-1
release of Linaro gdb 7.6.1, the first release in the 7.6.1 series.
This release is based on the latest upstream gdb 7.6 stable branch,
but with additional features and bug fixes.
#### Additional Features
* None
#### Bug Fixes
* Fixes for debugging on AArch64 with hardware breakpoints.
### Source
#### Release Tarball
* https://releases.linaro.org/13.09/components/toolchain/gdb-linaro
#### Development Tree
* git://git.linaro.org/toolchain/gdb.git
This release was built from the `linaro_gdb-7_6_1-2013_09-1_release` tag.
### Feedback and Support
Subscribe to the important Linaro mailing lists and join our IRC channels to
stay on top of Linaro development.
* Linaro Toolchain Development [mailing
list](http://lists.linaro.org/mailman/listinfo/linaro-toolchain)
* Linaro Toolchain IRC channel on irc.freenode.net at `#linaro-tcwg`
* Questions? [ask Linaro](http://ask.linaro.org/).
* Interested in commercial support? inquire at [Linaro
support](mailto:support@linaro.org)
--
Will Newton
Toolchain Working Group, Linaro