linaro-toolchain

linaro-toolchain@lists.linaro.org

6 participants
5578 discussions

[ACTIVITY] 8th - 14th August 2014

by Bernie Ogden

=Progress= cbuild2 benchmarking - TCWG-360 [4/10] * Some disagreements with gerrit * One of my patches broke bare metal builds (now fixed) * More review of the way we store benchmark sources Other - [5/10] * Meetings, mail, etc (featuring newlib build options, defaults, cbuild vs benchmark scripts) * Learned to use git-send-email, bent it to my will * Authentication pain on ARM-side Holiday - [1/10] =Plan= cbuild2 benchmarking * Finish source/data storage plan * Figure out how benchmark cross-running will work, get started on it Holiday next week (25th - 29th August)

10 years, 9 months

[Weekly] 11-15 AUG 2014

by Michael Collison

== This week == * TCWG-515 - Neon intrinsic testing part 1 (3/10) - Completed testing with internal compiler error discovered compiling with -Og and -g - GCC bugzilla report 62040 already exists for this issue * TCWG-518 - Neon intrinsic testing part 2 (2/10) - Completed testing with no regressions found * TCWG-519 - Neon intrinsic testing part 3 (2/10) - Completed testing with no regressions found * Reviewed branch merge of Linaro 4.8 and 4.9 with FSF trees (3/10] == Next week == * Continue with neon intrinsic testing * Investigate bug 373 - [gcc-4.9][android][armv8] internal compiler error * Develop outline for Linaro Connect presentation

10 years, 9 months

[ACTIVITY] 8th - 14th August 2014

by Venkataramanan Kumar

== Progress == * TCWG-180 Debugging - LTO bootstrap failure in Aarch64 with GCC 4.9. (6/10) Analyzed tree dumps between stage2 and stage3 compilers. Noted that extra gimple declarations in stage2 compiler. Also inline minimum parameters in gimple.c.048i.inline were different. Richard Beiner found that way we hash the string literals was different between stage2 and stage3 compilers. Tested the patch, he posted on trunk but it does not solve the comparison failures. Also GCC garbage collector parameters for expansion and maximum heap size varies between stage 2 and stage3. Setting this parameters to same value in stage2 and stage3 builds fixes bootstrap failures in Aarch64. These fixes are for trunk and stage 1 5.0. Ref: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62077 Still need to find a work around for release branches Testing these patches on AMD64 /Aarch64 machines. * Others (2/10) * Upstream patch review. * 1-1 Meeting Christophe. * Misc and internal meeting. * setup LLVM. * Friday national holiday (2/10). == Plan == * Continue LTO bootstrap issue. * Benchmark Core mark with LTO. * Upstream patch review. == MISC == None .

10 years, 9 months

[ACTIVITY] Week 31 - 32 - 33

by Yvan Roux

-------------------------------------------------------------------------------- Week 31 -------------------------------------------------------------------------------- Short week, one day off (2/10) == Issues == * none. == Progress == * Respinned Linaro GCC 4.9-2014.07 (1/10) * Linaro GCC 4.9 2014.08 (6/10) - Prepared backports for release (38 revisions) - validation on-going * Misc: (1/10) - Various meetings. -------------------------------------------------------------------------------- Week 32 -------------------------------------------------------------------------------- On vacation :) == Issues == * none. == Progress == * GCC 4.9 2014.08 (3/0) - Analysed backports validation results. - Committed all backports. -------------------------------------------------------------------------------- Week 33 -------------------------------------------------------------------------------- Still on vacation :) == Issues == * none. == Progress == * GCC 4.9 2014.08 (2/0) - Merged FSF 4.9 branch into Linaro one - Released 2014.08 source tarball * GCC 4.8 2014.08 (2/0) - Merged FSF 4.8 branch into Linaro one - Released 2014.08 source tarball == Next == * Back to work on Tuesday

10 years, 9 months

[ANNOUNCE] Linaro GCC 4.9 and 4.8 2014.08 released

by Yvan Roux

The Linaro Toolchain Working Group (TCWG) is pleased to announce the 2014.08 stable release of both Linaro GCC 4.9 and Linaro GCC 4.8 source package. With the imminent release of ARMv8 hardware and the recent release of the GCC 4.9 compiler the Linaro TCWG will be focusing on stabilization and performance of the compiler as the FSF GCC compiler. The Linaro TCWG provides stable[1] quarterly releases and monthly engineering[2] releases. Linaro GCC 4.9 2014.08 is the fifth Linaro GCC source package release and first stable one in the 4.9 series. It is based on FSF GCC 4.9.2-pre+svn213803 and includes performance improvements and bug fixes. Interesting changes in this GCC source package release include: * Updates to GCC 4.9.2-pre+svn213803 * Backport of [AArch64] Drop ISB after FPCR write. * Backport of [AArch64] Remove from arm_neon.h functions not in the spec * Backport of [AArch32] Fix check for __FAST_MATH in arm_neon.h * Backport of [AArch64] fix and enable non-const shuffle for bigendian using TBL instruction * Backport of [AArch64] Fix constraint vec_unpack_trunk * Backport of [AArch32] Cortex-A5 rtx costs table * Backport of [AArch32] Handle clz, rbit types in arm pipeline descriptions * Backport of [AArch64] Fix argument types for some high_lane* intrinsics implemented in assembly * Backport of [AArch64] Handle fcvta[su] and frint in RTX cost function * Backport of [AArch64] Prologue rewrite + performance. Linaro GCC 4.8 2014.08 is the fourteenth release in the 4.8 series and is in maintenance. Based off the latest GCC 4.8.4+svn213802 release, it includes performance improvements and bug fixes. Interesting changes in this GCC source package release include: * Updates to GCC 4.8.4+svn213802 * Backport of Fix [AArch32] for PR sanitizer/58543 * Backport of Fix [AArch64] for PR target/59744 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(a)linaro.org [1] Stable source package releases are defined as releases where the full Linaro Toolchain validation plan is executed. [2] Engineering source package releases are defined as releases where the compiler is only put through unit-testing and full validation is not performed.

10 years, 9 months

[ACTIVITY] 11 - 15 August 2014

by Will Newton

= Progress == * Upstream work (4/10, CARD-341) - Patch review (gdb, binutils) - glibc testsuites for ARM and AArch64 * Booting upstream kernel on Chromebook (4/10) - Tried u-boot path but Google's shipped NV u-boot is broken in several ways - Fall back to trying to boot a signed upstream kernel - Gets halfway through boot then seems to turn the regulators off * Malloc application benchmarking (2/10, TCWG-441) - Add pdf library benchmark to benchmark suite - Improve argument parsing and result plotting - Seem to be hitting some new issue with mounting memory cgroup within docker == Issues == * None == Plan == * Iron out issues with malloc benchmark framework * Get Chromebook booting -- Will Newton Toolchain Working Group, Linaro

10 years, 9 months

[ACTIVITY] Week 33

by Renato Golin

== Progress == * Benchmarks (CARD-716 2/10) - Wrapping up SPEC run, some results - Fix missing tests, running with -ffast-math * Toolchain (CARD-862 4/10) - A few more assembler fixes - http://llvm.org/PR20462 - http://llvm.org/PR20595 - Some vectorizer cleanups - http://llvm.org/PR20655 * Background (4/10) - Code review, meetings, discussions, etc. - Trying D01s again as buildbots == Plan == * Pick some more toolchain bugs to work on * Release 3.5 tests and benchmarks * Move bots to CMake, enable compiler-rt * Change compilation to make Clang/LLVM non-NEON by default * Enable D01s as buildbots

10 years, 9 months

[ACTIVITY] Week 33

by Zhenqiang Chen

== Issues == * None. == Progress == * Update "Keep constants in register when expanding" patch according to comments (TCWG-486, 3/10). * Refine ccmp patches since the old ones can not apply (TCWG-488, 2/10). * Check PR62151, it was exposed by my commit r211885. But the root cause was r208165. * R/M toolchain related work (5/10) == Plans == * Ping pending patches. == Planed leaves == * Aug. 18 - 26.

10 years, 9 months

configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES

by Črt Gorup

Hi, I am trying to build a working environment with Angstrom Linux, QT5 for Toradex Apalis iMX6 module and additional QT5 SDK for my host machine. The compilation of Angstrom with additional QT5 layer went fine. However, there are some problems when building toolchain for the host machine (command meta-toolchain-qt5). It seems that there is a problem with configuration of linaro gcc runtime 4.8. The reported error is: "checking dynamic linker characteristics... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES". The log file is in the attachment. Does anyone have any idea how to fix this problem? I am using Ubuntu 14.04. Thanks in advance, Crt Gorup

10 years, 9 months

Linaro arm-linux-gnueabihf-gdb versus Ubuntu gdb-multiarch

by ssinfod ssinfod

Hello, I'm trying to perform cross platform remote debugging from my x86 computer to a remote ARM device. (ex: Beagle Bone Black) I'm using Ubuntu 14.04 and Eclipse CDT. I installed the Ubuntu package gcc-arm-linux-gnueabihf but the gdb debugger is not in that package. Therefore, I'm wondering if I should use the Linaro toolchain (which include arm-linux-gnueabihf-gdb) or if I should install the Ubuntu gdb-multiarch package. What is the difference between gdb-multiarch and arm-linux-gnueabihf-gdb ? Is it better to use gdb-multiarch ? Thanks ssinfod

10 years, 9 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain