- linaro-toolchain - lists.linaro.org

by Renato Golin

== Progress == * EHABI - Turning EHABI on by default on non-Darwin ARM - Had to add some relocations to MCJIT - Re-enabled EH tests on test-suite - Check-all, self-hosting and test-suite bots green * Compiler-RT - Enabling RT+San libraries to compile on ARM - Changing Clang to look for the generic libraries (arm, not armv7l) * MCJIT - Remote protocol fixed, all tests passing on self-hosting bot - All tests re-enabled on ARM * Background - More IAS, Compiler RT patch reviews - Buildbot cleaning up before every build (more stable) - Cambridge LLVM Social - Rumours that LLVM can compile the kernel with the integrated assembler on ARM * Time - CARD-862 8/10 - Others 2/10 == Plan == * FOSDEM - Talking about LLVM auto-vectorization this Sunday * EHABI - ARM detected some conflicts with Dwarf stack unwinding, investigate Compiler-RT - Run test-suite, benchmarks, applications with it * IAS - Confirm the rumours about the kernel compiling clean - Pick up some remaining task to implement

11 years, 4 months

1
0
0 0

TARGET_ATOMIC_ASSIGN_EXPAND_FENV

by Kugan

I had a look at the missing target hook TARGET_ATOMIC_ASSIGN_EXPAND_FENV to fix the C11 memory model testcase in regressions in trunk. I looked at the x86 implementation of this target hooks and x86 has instructions (FNSTENV,FLDENV,FNSTSW,FNCLEX) for feholdexcept, feclearexcept and feupdateenv. Does ARM has something similar? Any pointers/links I can refer to. Please see the gcc internal documentation for the target hook below. — Target Hook: void TARGET_ATOMIC_ASSIGN_EXPAND_FENV (tree *hold, tree *clear, tree *update) ISO C11 requires atomic compound assignments that may raise floating-point exceptions to raise exceptions corresponding to the arithmetic operation whose result was successfully stored in a compare-and-exchange sequence. This requires code equivalent to calls to feholdexcept, feclearexcept and feupdateenv to be generated at appropriate points in the compare-and-exchange sequence. This hook should set *hold to an expression equivalent to the call to feholdexcept, *clear to an expression equivalent to the call to feclearexcept and *update to an expression equivalent to the call to feupdateenv. The three expressions are NULL_TREE on entry to the hook and may be left as NULL_TREE if no code is required in a particular place. The default implementation leaves all three expressions as NULL_TREE. The __atomic_feraiseexcept function from libatomic may be of use as part of the code generated in *update. Thanks, Kugan

11 years, 4 months

2
1
0 0

[ACTIVITY] 20 - 24 January 2014

by Christophe Lyon

== Progress == - releases (3/10) * GCC 4.7 and 4.8 releases done * more cbuild2 feedback - cross-validations (2/10) * followup * adding capability to test a patch over a given revision on several targets/cpu/fpu/runtestflags - libsanitizer on AArch64 (3/10) * most tests are now functional * still some errors in the GCC testsuite, to be analyzed (there are some timeouts, too despite using SSH multiplexing to the Foundation model) - misc (2/10): conf-calls and meetings == Next == - libsanitizer on AArch64: analyze errors, try QEMU == Future == On sick leave starting Feb 11th

11 years, 4 months

1
0
0 0

[Activity] 20 Jan - 24 Jan 2014

by Venkataramanan Kumar

== Progress == * Libc probes support for Aarch64 (2/10). Wrote a small patch for setjmp and longjmp LIBC probe. Requested "will newton" to test them . * Investigate "PGO" for Aarch64 (3/10). Bootstap testing GCC with PGO for GCC. Stage 2, feedback profile in progress. Ran coremark on foundation model with PGO. The benchmark builds with profile-generate and runs. "gcda" files are generated and uses them to profile. Profile generated runs does not run cleanly. Cross checking if the generated profile is valid. * Resubmmited libssp machine description support in GCC (2/10). * Cbuild2 discussed with rob, ryan on SYSROOT installation while building (1/10) cross compiler for aarch64. "SYSROOT" is expected to be in /opt/linaro, but cbuild2 does not do this by default. Misc (1/10) ------------- AMD internal meetings and did some investigations == Plan == - Run EMBCC benchmarks with -PGO enabled. - Follow up upstream libssp GCC discussions.

11 years, 4 months

1
0
0 0

[ACTIVITY] Week 4

by Yvan Roux

* 4 days week (university). == Issues == * none == Progress == * LRA on AArch32: o TCWG-343 : Make LRA the default for the ARM backend (3/10) - Looking backend places (ARM and AArch64) where reload_in_progress is used to verify if lra_in_progress is needed as well: Tested lot of configurations, testsuite results analysis ongoing. o TCWG-345 : Analyse performance of LRA for ARM. (0/10) - No progress this week. * GMP library AArch64 port review: (4/10) o Analyzing code generated from C generic implementation vs assembly. * Misc. (1/10) o Various meetings. == Next == * Child care (chickenpox) * Still some time spend at university * Continue on LRA and lib GMP

11 years, 4 months

1
0
0 0

[ACTIVITY] 20 - 24 January 2014

by Omair Javaid

== Progress == * Implemented per process hwbreakpoint and watchpoint cache for arm native targets. Also added a reference count for per thread hardware breaks. [TCWG-177] [7/10] * Travelled to Islamabad for Macau visa application. [3/10] == Plan == * Continue work on forking/vforking hardware breakpoints support for arm-native. Tweak hardware breakpoint cache and thread breaks reference count to get it in sync with linux-native. [TCWG-177]

11 years, 4 months

1
0
0 0

[ACTIVITY] 20 - 24 January 2014

by Kugan

== Misc == - Monday 27/01/2014 - Public holiday == Progress == - LP#1191909: gold and -flto always fails with an internal error on arm-linux-gnueabi* (2/10) - Reproduced it and Looking into the implementation for best fix. -c11-atomic-exec-5.c (4/10) - Issue is due to missing target hook and looking at implementing -LP#1270789: gcc 4.8: "invalid expression as operand" in aarch64 inline asm (2/10) - came-up with the patch. Still in the process of testing it. APM1 disc seems to be corrupt and that is holding this. - Benchmarking (1/10) - added -pgo for coremark - Set-up a Linux desktop (1/10) == Plan == - Continue with trunk daily regression - Fix assigned bugs

11 years, 4 months

1
0
0 0

[ACTIVITY] Week 04

by Zhenqiang Chen

== Issues == * None == Progress == * Investigate to duplicate shared compares to get more conditional compares. * Investigate to enable shrink-wrap for TARGET_APCS_FRAME. Still some ICE fails in regression tests. * Help on cbuilv2 eglibc multilib build issues. == Plans == * Tuning ccmp performance * Enable shrink-wrap for TARGET_APCS_FRAME. == Planed leaves == * Jan. 31 - Feb. 10.

11 years, 4 months

1
0
0 0

[Activity] Jan 20-26

by Rob Savoye

== Progress == * Improve binary releases produced by Cbuildv2. (6/10 TCWG-383) * Minor changes to source releases produced by Cbuildv2. (1/10) * Added support to Cbuild to use lsbcc for binary releases. (1/10) * Meetings. (1/10) * Started reviewing Kugan's benchmarking branch of Cbuildv2. (1/10) == Plan == * Build static gdbserver for target via Cbuildv2. * Add Win32 installer for Canadian cross built binary releases to Cbuildv2. (TCWG-381) * Once Jenkins has a node_selector for the new Beagle Board Blacks, get those working for native builds. (TCWG-379) * Get QEMU and Foundation Model running on TCWG x86_64 build slaves so Jenkins can use them for native builds. (TCWG-380)

11 years, 4 months

1
0
0 0

[ACTIVITY] 20 - 24 January 2014

by Will Newton

== Progress == * Add support for AArch32 ARMv8 16<->64bit VCVT to QEMU (2/10, TCWG-51) * Triage and report AArch64 gcc bug when building glibc with SystemTap (1/10) * Debug and submit patch for ARM libffi issue (1/10) * Add support for longjmp/setjmp Systemtap probes on ARM (4/10, TCWG-378) * Ported Python cffi package to AArch64, submitted upstream (1/10) * Fixed bug building glibc for armv4 (1/10) == Issues == * Broadband down for 3 hours on Wednesday afternoon == Plan == * Follow up QEMU patches and maybe post v2 * malloc -- Will Newton Toolchain Working Group, Linaro

11 years, 4 months

1
0
0 0

[ACTIVITY] Week 4

by Renato Golin

== Progress == * Compiler-RT - Changing CMake to make it compile on ARM - Reviewing long div/mod patches for ARMv4/v5/v6, testing and benchmarking * EHABI - Investigating EH code generation (landing pads, jump tables, libs) - Running test-suite EH tests, some failures * Background - Loads of patch reviews on IAS, build attributes, EHABI, compiler-rt - Planning the 3.4.1 release (the first patch-release of LLVM) * Time - CARD-862 8/10 - Others 2/10 == Plan == * Continue EHABI tests, try to turn it on by default * Continue working on RT's CMake for ARM * Prepare the FOSDEM 14 presentation

11 years, 4 months

1
0
0 0

[Weekly] 20-24 JAN 2014

by Michael Collison

== This week == - Completed merge of crypto backports from trunk to Linaro 4.8 branch: - 64-bit backports: 205092, 205383, 205384, 206114, 206115, 206117, 206118, 206149 - 32-bit backports: 206518 AND 206519 - Built and tested 32 and 64-bit compilers with crypto changes == Next week == - Submit backports for review using git review - New backports == Future ==

11 years, 4 months

1
0
0 0

[ACTIVITY] Jan 20 - 24 - 2014

by Ryan Arnold

== Progress == Deferred US Holiday (MLK day) from Monday to Tuesday * Debugged what was thought to be a cbuild2 problem but ended up being due to default enablement of multilib in gcc. (2/10) * Started working on adding mulit-lib support to cbuild2 (minimal configuration for installing headers). (8/10) [Jira card forthcoming] - Moved kernel headers installation to arch based directory in sysroot and then symlinked appropriate host include directories to common arch directories. - Figured out how to build multilib arm libraries for arm-none-linux-gnueabihf and arm-none-linux-gnueabi. == Plan == * Add cbuild2 scripting to build multilib libraries based on gcc -print-multi-lib * Figure out how to get gcc to select the correct multilib headers directory so that we don't need a merged include directory. == Issues == * None

11 years, 4 months

1
0
0 0

[ANNOUNCE] Linaro GCC 4.8 and 4.7 2014.01 released

by Christophe Lyon

The Linaro Toolchain Working Group is pleased to announce the release of both Linaro GCC 4.7 and Linaro GCC 4.8. As announced at Linaro Connect USA 2013 Linaro GCC is moving to a pattern of quarterly stable releases, with engineering releases in the intervening months. This is the first stable release, and contains no known regressions compared to the 2013.12 release. The next release of GCC 4.7 will be the 2014.04 stable release. There will be no engineering releases of GCC 4.7 in 2013.02 or 2013.03. The next stable release of GCC 4.8 will be the 2014.04 release. Next month's release - 2013.02 - will be an engineering build. Linaro GCC 4.7 2014.01 is the twenty second release in the 4.7 series. Based off the latest GCC 4.7.4+svn206380 release, this is the ninth release after entering maintenance. Interesting changes include: * Updates to GCC 4.7.4+svn206380 Linaro GCC 4.8 2014.01 is the tenth release in the 4.8 series. Based off the latest GCC 4.8.3+svn206350 release, it includes performance improvements and bug fixes. Interesting changes include: * Updates to GCC 4.8.3+svn206350 * Enhanced multilib support The source tarballs are available from: http://releases.linaro.org/14.01/components/toolchain/gcc-linaro/4.7 http://releases.linaro.org/14.01/components/toolchain/gcc-linaro/4.8 Downloads are available from the Linaro Releases website: http://www.linaro.org/downloads/ More information on the features and issues are available from the release pages: https://launchpad.net/gcc-linaro/4.7/4.7-2014.01 https://launchpad.net/gcc-linaro/4.8/4.8-2014.01 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

11 years, 4 months

1
0
0 0

[Activity Jan 13-19

by Rob Savoye

== Progress == * Got got Beagle Board blacks up, installed all necessary dependencies to build toolchains. (TCWG-379 - 1/10) * Installed QEMU and Foundation model on all TCWG x86_64 build slaves. (TCWG-380 - 1/10) * Minor bug fixes for Cbuildv2 produced source tarballs to be hopefully now 100% match with what we usually release. (2/10) * More major bug fixes and some refactoring for Cbuildv2 produced binary tarballs to match with what we usually release. (3/10) * Meetings. (1/10) == Plan == * Build static gdbserver for target via Cbuildv2. * More work on binary tarball building. * Add Win32 installer for Canadian cross built binary releases to Cbuildv2. (TCWG-381) * Once Jenkins has a node_selector for the new Beagle Board Blacks, get those working for native builds. (TCWG-379) * Get QEMU and Foundation Model running on TCWG x86_64 build slaves so Jenkins can use them for native builds. (TCWG-380) == Issues == * I got invited to Mt Everest last week... :-)

11 years, 4 months

2
2
0 0

[ACTIVITY] Week 3

by Yvan Roux

* 4 days week (still some times spent at university). == Issues == * none == Progress == * LRA on AArch32: o TCWG-343 : Make LRA the default for the ARM backend (3/10) - Most of the issues fixed or about to be fixed by Vladimir : * iWMMXT issue and Thumb1 udivmoddi4 : fixed. * Thumb1 code size issue : partial patch proposed. - Looking backend places (ARM and AArch64) where reload_in_progress is used to verify if lra_in_progress is needed as well. Validation ongoing. o TCWG-345 : Analyse performance of LRA for ARM. (0/10) - No progress this week. * Loop specialisation patch review: (1/10) o Sent feedback to Samsung. * 2014.01 release: (1/10) o Branch merge review * [Bug 1258013] Re: Cannot build arm64 kernel with CONFIG_DEBUG_INFO=y (1/10) o Issue due to a wrong .align directive in an assembly source file which is already fixed upstream. * GMP library sAArch64 port review: (1/10) o Started to review Anil work. * Misc. (1/10) o Various meetings. == Next == * Still some time spend at university * Continue on LRA and lib GMP.

11 years, 4 months

1
0
0 0

[ACTIVITY] 13-17 January 2013

by Christophe Lyon

- 2014.01 releases: (2/10) * 4.7 ready, 4.8 needed a short daily to include our multilib patch to support our binary releases. * retried cbuildv2 and sent feedback. Should be mostly OK by now. - cross-validations: (2/10) * followup-up, bugzilla * thinking about short term Neon intrinsics testsuite use without dejagnu - libsanitizer (2/10) * resumed work for aarch64 - misc (2/10): conf-call and meetings - internal support (2/10) * issue: boards used for benchmarking have been off for several weeks. Pending jobs disappeared from the list, but I got no log.

11 years, 4 months

1
0
0 0

[ACTIVITY] 13 - 17 January 2014

by Omair Javaid

== Progress == * Implement fork over HW breaks support for arm native targets. [TCWG-177] [6/10] * ARM Process Record: - All patches accepted and upstream. - Spent time making changes to VFP, SIMD etc patch. [2/10] - Configuration and Git ssh setup for gdb commit rights . [1/10] * Submitted a new fix and worked with community for the fix. [1/10] == Plan == * Continue to work on fork over HW breaks support for arm native targets. [TCWG-177] * Patch updates and submission to all in progress upstream submissions. * Travel to Islamabad for Macau visa application.

11 years, 4 months

1
0
0 0

[Activity] 13 Jan - 17 Jan 2014

by Venkataramanan Kumar

== Progress == * Libc probes support for Aarch64. Testing the patch for "libc" probes support to "__longjump". Native compiling in openemebedded. Obtained a Linaro open embedded image with system tap enabled. Getting Assembler Error during "malloc" module linking in "glibc" configured with --enable-systemtap. In libc_mallopt invalid "asm", invalid expression as operand for LIBC_PROBE call. Cross compiling. Tried copying header files from system tap source to SYSROOT for cross compiling glibc. The cross compiled GCC does not recognize the header files. * Investigate "PGO" for Aarch64. Started bootstap testing GCC with PGO for GCC. Stage 1 completed. stage profile in progress. == Plan == - Run EMBCC benchmark with -PGO enabled. - Work on "glibc" probe. == Issues == Waiting for feedback on "libssp" machine descriptions changes. Misc ------ 14-Jan-2014 Local holiday.

11 years, 4 months

1
0
0 0

[ACTIVITY] 13 - 17 January 2014

by Kugan

== Progress == - TLS GOT binutils patch and gcc fix for aarch64_build_constant are committed upstream. (1/10) - TCWG-360 (closed) (1/10) - TCWG-349 (closed) (4/10) - set-up trunk daily regression (4/10) - Resolved issues running address sanitiser with qemu - started running daily cross regression testing with qemu and native regression testing on chromebook. - Started analysing failures. == Plan == - Continue with trunk daily regression - Look at pending optimization cards

11 years, 4 months

1
0
0 0

[ACTIVITY] Week 03

by Zhenqiang Chen

== Issues == * None. == Progress == * Test Linaro cbuildv2. - Write a reference script to support windows installer in cbuildv2. - Do some basic validation work against the binaries built from cbuildv2. * Reproduce and work out a patch for "ICE when building linux-linaro-tracking" (lp:1268893, PR59837) . * Test to merge Linaro local armv4t multilib patch to Linaro 4.8. * Investigate CCMP chance by taking a Bool_ var as var != 0. == Plans == * cbuildv2 validation * Tuning ccmp performance == Planed leaves == * Jan. 31 - Feb. 9.

11 years, 4 months

1
0
0 0

[Weekly] 13-17 Jan 2014

by Michael Collison

== This week == - Completed merge of crypto backports 206128, 206130, 206131, 206132 and 206149 from trunk to Linaro 4.8 branch - Out sick Friday == Next week == - Build and test crypto backports - Begin merging aarch64 crypto backport to Linaro 4.8 branch == Future ==

11 years, 4 months

1
0
0 0

[ACTIVITY] Week 3 (Jan 13-17 2014)

by Ryan Arnold

== Progress == * Cbuildv2 fix for *_release() functions which were changing out of the build directory but then not changing back to the builddir, which caused problems with paths relative to the builddir. (1/10) * TCWG-340 Enable Glibc remote testsuite integration - (7/10) - Working with upstream community on scoping and designing remote testsuite integration. - Setting up arm chroot environment on chromebook with documentation on how to make this reproduceable. * TCWG-352 AArch64 clone is missing some CFI markup - (2/10) - Setup aarch64 environment for testing and built static clone tests to test the patch. == Plan == * Start implementing (code) for glibc remote testsuite integration. == Issues == None

11 years, 4 months

1
0
0 0

[ACTIVITY] Week 3

by Renato Golin

== Progress == * Buildbots - Odroid U2 died after a few days on USB stick, too. (I guess we're stuck with Chromebooks) - Upgrading chromebooks (to Saucy) due to a new GCC/libstdc++ 4.7+ restriction - Shuffling chromebooks, we now have three buildbots: - llvm-chrome-01: quick-build+check - llvm-chrome-02: self-host+check - llvm-chrome-03: test-suite * MCJIT Remote - Re-factored the communication protocol of MCJIT for remote processes - Still seeing one random failure on ARM, investigating * Compiler-rt - Investigating how to get it compiling all libraries and sanitizers on ARM * Background - Patch reviews, especially IAS and EH * Time - CARD-862 8/10 - Others 2/10 == Plan == * Continue MCJIT and Compiler-RT investigations * Continue reviewing IAS and EH patches * Try to run the EH tests on the test-suite with the current changes

11 years, 4 months

1
0
0 0

[ACTIVITY] 13 - 17 January 2014

by Will Newton

== Progress == * Add support for AArch32 ARMv8 VRINT to QEMU (4/10, TCWG-50) * Add support for AArch32 ARMv8 VCVT to QEMU (4/10, TCWG-49) * Add support for AArch32 ARMv8 16<->64bit VCVT to QEMU (1/10, TCWG-51) * Fixed gas ARM VCVT encoding bug (1/10) == Issues == * None == Plan == * Complete outstanding QEMU work * ARM setjmp/longjmp SystemTap probes * malloc -- Will Newton Toolchain Working Group, Linaro

11 years, 4 months

1
0
0 0

ICE when building linux-linaro-tracking

by Koen Kooi

Hi, I've been playing with linux-linaro-tracking and the 2013.12 (and 2013.10, 2013.11) toolchain release and when turning on the NEON in kernel option I get: CC lib/raid6/neon4.o lib/raid6/neon4.c: In function 'raid6_neon4_gen_syndrome_real': lib/raid6/neon4.c:113:1: internal compiler error: in dwarf2out_frame_debug_adjust_cfa, at dwarf2cfi.c:1078 } ^ Use the attached .txt as .config and do 'make zImage' to replicate the problem. You will probably need to attached patch as well since some of the linaro patches break namespace support :( regards, -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs

11 years, 4 months

3
8
0 0

[ACTIVITY] Week 2

by Yvan Roux

* Two days week (due to compilation courses given at university). == Issues == * none == Progress == * LRA on AArch32: o TCWG-343 : Make LRA the default for the ARM backend (1/10) - iWMMXT issue : back on the issue. - Thumb1 issues : looked at bugzilla's reports. o TCWG-345 : Analyse performance of LRA for ARM. (0/10) - No progress this week. * Loop specialization patch review: (1/10) o Back on the task. * [Bug 1258013] Re: Cannot build arm64 kernel with CONFIG_DEBUG_INFO=y (1/10) o Tried to reproduce the issue. * Misc. (1/10) o Catching up with email, etc o Meeting == Next == * Still some time spend at university * Continue the ongoing tasks. * Branch merge reviews.

11 years, 4 months

1
0
0 0

[ACTIVITY] 6 - 10 January 2014

by Omair Javaid

== Progress == * ARM Process Record: - Follow up on patches, almost all patches accepted. [0.5/10] - Got GDB committ rights and set up git for pushing patches. [0.5/10] * Spent time to read through fortran functions prologue to find a new fix for TCWG-267. [1/10] * Initial investigation of handling breakpoint over fork [TCWG-177] [1/10] * Getting documentation ready for Macau visa application [2/10] == Plan == * Update and send patches where required and committ all approved patches. * Work on breakpoints issues [TCWG-177] and reverse stepping through solib issue [TCWG-315] * Apply for Macau visa, given all documents get ready.

11 years, 4 months

1
0
0 0

[Activity] 06 Jan - 10 Jan 2014

by Venkataramanan Kumar

== Progress == * Libc probes support for Aarch64. Posted patch for "libc" probes support to "__longjump". Worked on review comments from Maintainers. Upstream discussions in progress. Working on testing "glibc" by using --enable-systemtap. * Experimented with "Cbuildv2" native building. == Plan == - Continue Cbuildv2. - Investigate "PGO" for Aarch64. - Work on "glibc" probe. == Issues == Waiting for feedback on "libssp" machine descriptions changes. misc === 14-Jan-2014 leave.

11 years, 4 months

1
0
0 0

[ACTIVITY] 6-10 January 2014

by Kugan

== Progress == - Zero/sign extension elimination - experimented and discussed upstream. Still no confirmation (2/10) - Bug investigation LP1267122 and LP1263576 (6/10) - CBUILD2 Benchmarking (2/10) - More testing on chrome book == Plan == - Finish CBUILD2 Benchmarking - set-up trunk daily regression

11 years, 4 months

1
0
0 0

[ACTIVITY] Week 2

by Zhenqiang Chen

== Issues == * None. == Progress == * Try cbuildv2 and compare the binaries with current releases. * Identify MULTIARCH_DIRNAME in trunk breaks aarch64 multiarch build. * Branch-cost tune for Cortex-M. == Plans == * Verify binaries built from cbuildv2 == Planed leaves == * Jan. 30 - Feb. 10.

11 years, 4 months

1
0
0 0

[ACTIVITY] Week 1 - Jan 6 - 10

by Ryan Arnold

== Progress == * Draft wiki page (under ACL--let me know if you want to see) for instructions for setting up chroots on chromebooks for glibc testing: https://collaborate.linaro.org/display/~ryan.arnold@linaro.org/Configuring+… * Investigated expanding remote testing possibilities in glibc. * RFC email to libc-alpha discussing proposal for glibc host testsuite in chroots: https://sourceware.org/ml/libc-alpha/2014-01/msg00222.html == Issues == * Shortened week (3-days) because of unplanned school closures on Monday and Tuesday due to freezing temperatures, during which I had to watch my kids. == Plan == * Start code scaffolding for glibc host testsuite in chroot. * Start cbuild2 scaffolding for building remote chroots for glibc testing. * Add glibc multi-lib builds and IFUNC system libraries. * Work on cbuild2 support for local tar files.

11 years, 4 months

1
0
0 0

[Weekly] 06-10 JAN 2014

by Michael Collison

== This week == - Completed local backportS of 201164, 201165, 201166, 201167, 201168. == Next week == - Complete backport of 201175 - Submit merge requestS using git == Future ==

11 years, 4 months

1
0
0 0

[ACTIVITY] Week 1

by Will Newton

== Progress == * Two day week * Catching up on email etc. after break (0.5/10) * Investigate setjmp/longjmp SystemTap probe support in ARM glibc (1/10, TCWG-378) * Investigate toolchain bug reports for ARM and AArch64 (0.5/10) == Issues == * None == Plan == * Resume QEMU ARMv8 AArch32 work * Hopefully push glibc ARM pointer encryption fix for 2.19 -- Will Newton Toolchain Working Group, Linaro

11 years, 4 months

1
0
0 0

[ACTIVITY] 6-10 January 2014

by Christophe Lyon

- 2013.12 releases (1/10) * Sent announcements for 4.7 and 4.8 releases. - 2014.01 releases (2/10) * Created 4.7 and 4.8 branch merge requests (had handle some conflicts in 4.8) * Looked at backporting the crypto intrinsics support into 4.8, but there are dependencies with several other patches we haven't backported yet. - cross validation (4/10) * Restarted them since I had to stop them during the holidays. Still catching up with the backlog, should be OK during the week-end. * Analyzed and reported several regressions or new tests failing in some configurations. - Neon intrinsics tests (1/10) * Looked at Rob's neon-intrinsics branch and sent him some feedback. - misc (2/10): conf-calls and meetings. == Next == - 2014.01 releases - cross-validation: look at results and report regressions if any - resume libsanitizer work for AArch64

11 years, 4 months

1
0
0 0

[ACTIVITY] Week 01

by Renato Golin

== Progress == * Release 3.4 went out * Buildbots - Using powered USB hub for the external harddrive, but all boards fail one time or another... - Maybe it's the hard-drive type (mobile, power-saving), reverting to USB sticks for now - Leaving an odroid U2 running on USB stick for a week, used to work... - C++11 features will need GCC 4.7+, looking for an easy way to upgrade the Chromebooks * MCJIT - Finished work on remote MCJIT to re-enable the failing tests - http://llvm-reviews.chandlerc.com/D2527 * Pragma Vectorize - New discussions hint that my parser patch is moot, for now - Agreement is to use C++11 attributes for now, and add pragmas later - I can't continue implementing them, though... * Background - Huge number of patch reviews during holidays & this week - Good progress on new features for the IAS - More progress on EHABI, including IAS support * Time - CARD-862 8/10 - Others 2/10 == Plan == * Continue reviewing IAS features, maybe implement some * Work out how to create a libcxx bot * re-introduce llvm-chrome-01 as second self-host * Migrate all buildbots to GCC 4.7+ * Check out EHABI tests and assess progress

11 years, 4 months

1
0
0 0

miscompilation of unsigned comparison on aarch64

by Michael Hudson-Doyle

Hi, I filed this on bugzilla: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59744 but I thought I'd mention it here too. This slightly strangely written program (it's distilled down from frame_offset_overflow in the gcc source itself) should print "bigger" if the first argument is bigger than 10 (or negative, but let's ignore that please): #include <stdlib.h> #include <stdio.h> int a[2] = { 10, 20 }; int is_bigger (long offset, int index) { unsigned long size = -offset; if (size > a[index]) { printf("bigger\n"); return 1; } return 0; } int main (int argc, char** argv) { long v; v = atol(argv[1]); is_bigger(-v, 0); return 0; } When compiled at -O1 or above (and with inlining disabled at -O2 and above), though, it bungles the 0 case: (t-doko)mwhudson@arm64:~$ gcc-4.9 -O3 test.c -o test -fno-inline -Wall (t-doko)mwhudson@arm64:~$ ./test 1 (t-doko)mwhudson@arm64:~$ ./test 11 bigger (t-doko)mwhudson@arm64:~$ ./test 0 bigger (t-doko)mwhudson@arm64:~$ gcc-4.9 -O0 test.c -o test -Wall (t-doko)mwhudson@arm64:~$ ./test 1 (t-doko)mwhudson@arm64:~$ ./test 11 bigger (t-doko)mwhudson@arm64:~$ ./test 0 (t-doko)mwhudson@arm64:~$ What's going on? Here's the disassembly of is_bigger (at O3): 0000000000400608 <is_bigger>: 400608: b0000082 adrp x2, 411000 <_GLOBAL_OFFSET_TABLE_+0x28> 40060c: 91010042 add x2, x2, #0x40 400610: a9bf7bfd stp x29, x30, [sp,#-16]! 400614: 52800003 mov w3, #0x0 // #0 400618: 910003fd mov x29, sp 40061c: b8a1d841 ldrsw x1, [x2,w1,sxtw #2] 400620: ab00003f cmn x1, x0 400624: 540000a2 b.cs 400638 <is_bigger+0x30> 400628: 90000000 adrp x0, 400000 <_init-0x3f8> 40062c: 911b6000 add x0, x0, #0x6d8 400630: 97ffff90 bl 400470 <puts@plt> 400634: 52800023 mov w3, #0x1 // #1 400638: 2a0303e0 mov w0, w3 40063c: a8c17bfd ldp x29, x30, [sp],#16 400640: d65f03c0 ret Basically it seems that the condition "-offset > val" is being compiled as "val + offset does not overflow", which is not valid for offset == 0. This seems to me to be the underlying cause behind https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1263806 ("gccgo fails to compile tomb.go on arm64"). Cheers, mwh

11 years, 4 months

1
0
0 0

help on linaro android toolchain 13.12 (arm-v7)

by Sandeepa Prabhu

Hi, We are trying to build android Kitkat (for our own platform) using linaro android toolchain version 4.7.4 from 13.12 release. We are observing following while compiling some shared libraries: ~arm-linux-androideabi-4.7/bin/../libexec/gcc/arm-linux-androideabi/4.7.4/real-ld: warning: shared library text segment is not shareable ~arm-linux-androideabi-4.7/bin/../libexec/gcc/arm-linux-androideabi/4.7.4/real-ld: error: treating warnings as errors We tried to suppress thisn warning by setting LDFLAGS but the tool-chain does not seem to identify this flag: LOCAL_LDFLAGS := --no-warn-shared-textrel We need some help to fix this, so posting on both android and tool-chain mailing lists. Thanks, Sandeepa

11 years, 4 months

2
1
0 0

LLVM and GCC working together

by Renato Golin

Hi folks, As most of you are on the GNU side of the fence, I believe this is the right crowd to first ask this question, before attempting a wider audience. For a while, Clang/LLVM wasn't in any position to add unheard-of features, and most of what we needed would be covered by something GCC already did. But in the last year or so, there were a number of "features" we'd like to add that aren't present in GCC (like pragmas, attributes, asm directives) which is neither part of the language specifications, nor something that another standard (like OpenMP or ABIs) already support. As a concrete example, we're trying to come up with some vectorisation annotation and there is a heated discussion on whether it should be C++11 attributes, pragmas, or changing the __attribute__ semantics to allow it to be used in lexical blocks, not just declarations. Any of that, but most strikingly the latter, would add Clang-specific behaviour which GCC probably won't implement, and we all know how that feels. In this discussion, and others regarding ARM-specific behaviour (notably about assembly directives), I have used the same argument twice already, so it's time to ask the GCC crowd once and for all: For non-standard, domain or platform specific changes, do we want to have a joint task force, GCC+LLVM, to homogenize the efforts in extending the languages we support in the same say, so that we can call it the "OSS Compiler Extensions" (or whatever) instead of two separate GCC-extensions and Clang-extensions? Historically, GCC has *a lot* more extensions, so this new standard would probably be 99% GCC, but the goals of such a task force for the future would be to: 1. Make sure all OSS compilers implement the same extensions, when they so chose. So, extensions to the language should go in a shared forum, and not to Clang/GCC lists. 2. Document each extension and record all discussions (threads, bugs, etc), so that new compilers can have an easier time implementing them. 3. Reason about the existing hazardous or redundant extensions, and mark them for deprecation. This is also pertinent to the Linux kernel, which is driving its own task force to compiler the kernel with Clang, so that it can rid itself from outdated GNU extensions that lingered for far too long in their code. I appreciate the size of this proposal, the political issues and the endless discussions, but this is the same on every standard committee, and I'd rather have something than nothing at all. Perhaps, as it happened before, some of these changes could be more easily persuaded to move back to the language standards and platforms ABIs, than if it's just implemented, undocumented, by one compiler. So, ignoring just for a moment the political side of it, would that make technical sense for the GCC community as well? cheers, --renato

11 years, 5 months

1
0
0 0

Stable GCC

by Renato Golin

Folks, Since LLVM is moving on to C++11, I need to replace our buildbot GCCs with 4.7+ (the new minimum requirement), but I'd like to use whatever is the most stable and modern GCC version for native compilation. I could get the latest and greatest on our repository, but I know how compilers are written, and pardon me if I don't trust new releases... ;) Does any one have an opinion on which is the most stable, preferably 4.8, release of native ARMv7 GCC binaries? For some odd reason, we just release cross-compilers, so, in that case, where would I look for a native GCC, other than in my Ubuntu/Arch repositories? ARM? CodeSourcery? I *really* don't want to compile it myself... My lack of available fast ARM hardware is disturbing, and I don't want to spend a week cross-compiling GCC. cheers, --renato

11 years, 5 months

1
0
0 0

[ANNOUNCE] Linaro GCC 4.8 and 4.7 2013.12 released

by Christophe Lyon

The Linaro Toolchain Working Group is pleased to announce the release of both Linaro GCC 4.8 and Linaro GCC 4.7. Linaro GCC 4.7 2013.12 is the twentiy first release in the 4.7 series. Based off the latest GCC 4.7.4+svn205768 release, this is the eighth release after entering maintenance. Interesting changes include: * Updates to GCC 4.7.4+svn205768 * Fixed MULTILIB_DEFAULTS in linux-eabi case. Linaro GCC 4.8 2013.12 is the ninth release in the 4.8 series. Based off the latest GCC 4.8.3+svn205577 release, it includes performance improvements and bug fixes. Interesting changes include: * Updates to GCC 4.8.3+svn205577 * AArch64: enable build of libjava and libatomic. Change frame growth direction, thus enabling libssp build. The source tarballs are available from: http://releases.linaro.org/13.12/components/toolchain/gcc-linaro/4.7 http://releases.linaro.org/13.12/components/toolchain/gcc-linaro/4.8 Downloads are available from the Linaro Releases website: http://www.linaro.org/downloads/ More information on the features and issues are available from the release pages: https://launchpad.net/gcc-linaro/4.7/4.7-2013.12 https://launchpad.net/gcc-linaro/4.8/4.8-2013.12 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

11 years, 5 months

1
0
0 0

[Activity] 30 DEC-03 Jan 2013

by Venkataramanan Kumar

== Progress == * Pointer mangling Aarch64 glibc. Worked on review comments from Maintainer. Rebased and posted the patch. Upstream completed and closed the card. https://cards.linaro.org/browse/TCWG-373 * Experimented with Cbuildv2 native building. == Plan == - Continue Cbuildv2. - Investigate PGO for Aarch64. == Issues == Waiting for feedback on libssp machine descriptions changes.

11 years, 5 months

1
0
0 0

[ACTIVITY] Week 01

by Zhenqiang Chen

== Issues == * None == Progress == * One day off (Jan. 1) * Do some basic validations for 2013.12 toolchain binaries release. * R/M Mac toolchain validation * Branch-cost related tuning for Cortex-M. == Plans == * Continue on branch-cost related tuning.

11 years, 5 months

1
0
0 0

[ACTIVITY] 30 December 2013 - 3rd January 2014

by Kugan

== Progress == - Short week (4 Days) - TCWG-291 zero/sign extension elimination 4/10 - made re-factoring and ran the regression - benchmarking in progress - TCWG-134 divmod 4/10 - converted into latest pass structure and re-based the patch - found some regression failures and fixed them - regression testing ongoing == Plan == - post divmod and vrp patches

11 years, 5 months

1
0
0 0

[ACTIVITY] 30 December 2013 - 3rd January 2014

by Omair Javaid

== Progress == * ARM Process Record: [TCWG-336] [TCWG-338] [TCWG-339][TCWG-317] [TCWG-315] - Configured and learnt to use git format-patch and git send-email. [1/10] - Incorporated and tested changes suggested by maintainers in previous arm process record patches. [2/10] - Created a new patch series indicating bug fixes separate from features. [1/10] - Submitted version 2 of arm process record replay improvements. * Debugging of stepping over and single stepping heurisitic code. [TCWG-315] [4/10] * Review of open JIRA cards and pending patches [1/10] * Time off for setting up new office space. [0.5/10] * Macau visa information gathering and document preparation [0.5/10] == Plan == * Reverse engineering stepping code heuristics in gdb to find a fix for reverse debugging of solib code on arm. [TCWG-315] * Find and submit a new fix for TCWG-267. * New office space setup and Macau visa application, will be away from my desk for few hours.

11 years, 5 months

1
0
0 0

[ANNOUNCE] Linaro Toolchain Binaries 2013.12 released

by Bernhard Rosenkränzer

Just before having to rename it to 2014, the Linaro Toolchain and Builds and Baselines Working Groups are pleased to announce the 2013.12 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.8 2013.12 * Linaro GDB 7.6.1 2013.12 * Linaro Binutils 2.24 2013.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: * Binutils has been updated to 2.24, bringing many improvements * Various bugs have been fixed 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://releases.linaro.org/13.10/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.

11 years, 5 months

1
0
0 0

[Activity] 23-27 DEC 2013

by Venkataramanan Kumar

== Progress == * Pointer mangling Aarch64 glibc. Posted patch on pointer mangling. Worked on review comments from maintainer. Tested on V8 foundation model. == Plan == - Continue working on review comments for Pointer Guard support in Aarch64 glibc, - Continue Cbuildv2. - Investigate PGO for Aarch64. == Issues == Waiting for feedback on libssp machine descriptions changes.

11 years, 5 months

1
0
0 0

[ACTIVITY] Week 52

by Zhenqiang Chen

== Issues == * None == Progress == * One day off (Dec. 27). * Prepare toolchain binaries release - Backport the newlib patches for ftruncate() and truncate() stubs - Test and update binutils version to linaro-2.24-2013.12 and workaround gold compile fail issue. * Retest -fira-loop-pressure performance on cortex-m4. But get regression in several suites of eembc-v1. Will re-investigate it when aarch64 performance test is ready since it is enabled in ia64 and rs6000, and the comment says: /* Numerous experiment shows that IRA based loop pressure calculation works better for RTL loop invariant motion on targets with enough (>= 32) registers. It is an expensive optimization. So it is on only for peak performance. */ * R/M toolchain related work. == Plan == * Linaro toolchain binaries 2013.12 release

11 years, 5 months

1
0
0 0

[ACTIVITY] 23 - 27 December 2013

by Kugan

== Progress == - Short week (25th and 26th public holidays) - Integrate benchmarking into Cbuildv2 (TCWG-360 4/10) - First cut implementation complete and ready for review - Binutils Bug 16340 (2/10) - Posted modified patch after regression testing and analysing the results == Plan == - ping modified zero/sign extension patch with benchmarking - set-up trunk daily regression testing - start TCWG-238

11 years, 5 months

1
0
0 0

[ACTIVITY] 23 - 27 December 2013

by Omair Javaid

== Progress == * ARM Process Record made the changes pointed out in maintainers comments. [3/10] [TCWG-336] [TCWG-338] [TCWG-339] - Put the new bug fixes patches on hold as they can be sent in the same series.[TCWG-317] [TCWG-315] * Time off for setting up new office space. [4/10] - Found a good room for office in a central location, need to get internet and other stuff working before shifting. I will get started on that once I get the possession of the space next week. * Time off for Macau visa information [1/10] * 25th December Public Holiday [2/10] == Plan == * ARM Process Record: - Create new patches as per maintainers suggestions, incorporating bug fixes as separate patches in the list. - Test and send all patches upstream. * New office space setup, will be away from my desk for few hours.

11 years, 5 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain