== 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
== Progress ==
* Toolchain (CARD-862 2/9)
- Investigating LLD, MCLinker
* Automation Framework (CARD-1378 4/9)
- Lots of validation and lab meetings
- Planning and designing a new rack:
- Replace all chromebooks with D01s
* Background (3/9)
- Code review, meetings, discussions, etc.
- A bit more on Cauldron's presentation
- Revamping LLVM plan, TCWG mission, Validation docs
* Some illness...
== Plan ==
More rack stuff... Monday holiday.
== Progress ==
* Patch review, testing and follow-up (3/10, CARD-341)
- glibc 2.20 freeze still not announced
- submit more warning fix patches
- reviewed series of gdb thumb prologue patches
* Get postgresql malloc benchmark using unix domain sockets (2/10, TCWG-441)
* Built releases of eglibc and binutils for 2014.07 (3/10)
* Started looking at moving binutils and gdb bugs in launchpad to
bugzilla (1/10)
* Other small things (1/10)
- Investigated a couple of other small issues for various people
- Meetings
== Issues ==
* None
== Plan ==
* Clear up more old bugs and move to bugzilla/JIRA/upstream
* malloc benchmarking
* glibc patches
--
Will Newton
Toolchain Working Group, Linaro
The Linaro Toolchain Working Group is pleased to announce the 2014.06
release of Linaro GCC 4.7.
As announced at Linaro Connect USA 2013 Linaro GCC moved to a pattern
of quarterly stable releases, with engineering releases in the
intervening months. This is the third stable release, and contains no
known regressions compared to the 2014.04 release.
Linaro GCC 4.7 2014.06 is the twenty forth release in the 4.7 series.
Based off the latest GCC 4.7.5+svn211571 release, this is the eleventh
release after entering maintenance and the final one.
Interesting changes include:
* Updates to GCC 4.7.4+svn211571
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
* Bug reports should be filed in Launchpad against "Linaro GCC
project":http://bugs.launchpad.net/gcc-linaro/+filebug.
* Questions? "ask Linaro":http://ask.linaro.org/.
* Interested in commercial support? inquire at "Linaro
support":mailto:support@linaro.org
