- linaro-toolchain - lists.linaro.org

[ANNOUNCE] Linaro Binary Toolchain Release-Candidate GCC 4.9-2016.02-rc1

by Ryan Arnold

The Linaro Binary Toolchain ============================ The Linaro GCC 4.9-2016.02-rc1 Release-Candidate is now available. Notice: All Linaro GCC 4.9 series toolchain users should migrate to the latest version of the Linaro GCC 4.9 toolchain in order to mitigate potential security exposure to CVE-2015-7545. See the NEWS section below for details. Download release-candidate packages from: http://snapshots.linaro.org/components/toolchain/gcc-linaro/4.9-2016.02-rc1/ http://snapshots.linaro.org/components/toolchain/binaries/4.9-2016.02-rc1/ Previous snapshots and release-candidates are at: http://snapshots.linaro.org/components/toolchain/binaries/ Previous releases are at: http://releases.linaro.org/components/toolchain/binaries/ Host Requirements ================== Linaro officially supports the current and previous Ubuntu LTS releases (as of the time of this release). This does not mean that the toolchain will not work on other/older Linux distributions. See the following for the life-time of Ubuntu LTS releases. https://wiki.ubuntu.com/Releases The host system upon which the cross-compiler will run requires a minimum of glibc 2.14, because of API changes to glibc's memcpy API. https://bugs.linaro.org/show_bug.cgi?id=1869 Package Versions ================= Linaro GCC 4.9-2016.02-rc1 FSF eglibc 2.19 (eglibc.git/linaro_eglibc-2_19) Linaro newlib 2.1.0-2014.09 (linaro_newlib-branch) Linaro binutils 2.24 (linaro_binutils-2_24-branch) FSF GDB 7.10 (gdb-7.10-branch) Linaro Linux Version 3.17-2014.10 (linux-linaro-3.17-2014.10) Linaro toolchain package git branches are hosted at: http://git.linaro.org/?a=project_list&s=toolchain%2F&btnS=Search NEWS for Linaro GCC 4.9-2016.02-rc1 ==================================== * Applied fix for CVE-2015-7545 - A stack-based buffer overflow in glibc's getaddrinfo() was corrected in glibc 2.23 and backported into Linaro eglibc 2.19 (linaro_eglibc-2_19). https://sourceware.org/ml/libc-alpha/2016-02/msg00416.html * See the following Linaro GCC snapshot: http://snapshots.linaro.org/components/toolchain/gcc-linaro/4.9-2015.10/ Contact Linaro =============== File bugs at http://bugs.linaro.org For Linaro member support see http://support.linaro.org For Linaro community support email linaro-toolchain(a)lists.linaro.org -- Ryan S. Arnold | Linaro Toolchain Engineering Manager ryan.arnold(a)linaro.org | ryanarn on #linaro-tcwg @ freenode.irc.net

9 years, 4 months

1
0
0 0

[ACTIVITY] 21-25 March 2016

by Christophe Lyon

== Progress == * Validation - extended validation: updated ABE patch after review - investigating how to actually separate stdout/stderr streams in dejagnu - still seeing random results (mostly in the sanitizers tests) in the Cambridge lab * GCC - no progress on Win32-hosted toolchain bug: cannot reproduce it from a manually built toolchain - advSIMD/Neon intrinsics tests: cleanup on-going - bug 2125: forwarded upstream, quickly fixed by R.Biener, backport in progress - Misc (conf-calls, meetings, emails, ...) == Next == * Validation: - more on extended validation - random tests investigation - more on stdout/stderr * GCC: - trunk monitoring, report regressions if needed - intrinsics tests cleanup

9 years, 4 months

1
0
0 0

[ACTIVITY] Week 12

by Yvan Roux

o Easter Monday off (2/10) == Progress == o Extended validation (5/10) * Worked on benchmarking integration * Analyzed failures due to --tarbin and --check ABE's flags * Analyzed native AArch32 timeout (due to guality/GDB testcase) o Misc (3/10) * Various meetings == Plan == o Continue on extended validation o Finalize DejaGNU patches, GCC ARMv8.1 builtins fix.

9 years, 4 months

1
0
0 0

[ACTIVITY] 21 - 25 March 2016

by kugan

== Progress == * Type promotion pass (6/10) - Fixed major false positive uninit warnings = Changed tree-ssa-uinit to handle SEXT_EXPR = preserving TREE_NO_WARNING set by SRA = Somemore fixes to preserve debug loc - There are still some more but this is mainly due to how tree-ssa-uinit is designed - Working through the output patterns; some are simple changes but some needs more analysis - Planning to create a branch with the latest version for easy review * Bugs (1/10) - PR70359 * Misc (1/10) - GCC Lists * Public holiday (2/10) == Plan == * Type promotion pass benchmarking * Perf with LTO

9 years, 4 months

1
0
0 0

[Weekly] 21-25 March 2016

by Michael Collison

== This week == * Bugzilla 69663 - [ARM] Implement overflow arithmetic standard names (4/10) - Resolved all thumb2 failures - Posted new patch upstream * TCWG-247 - Create Validation Job to run on GCC Trunk Commits (1/10) - Investigation into Python API for discovering when Jenkins builders are idle * Laptop hardware failure debugging (2/10) - Requested a new laptop from Arm * Misc meeting (1/10) * Good Friday holiday (2/10) == Next week == * TCWG-247 - Create prototype implementation

9 years, 4 months

1
0
0 0

[ACTIVITY] 21 - 25 March 2016

by Prathamesh Kulkarni

== This Week == * LTO (4/10) - Committed r234490 to fix PR70366 - Spent unnecessary time tracking down known (invalid) bug PR65778 - LTO and branch out of range error: - patch to introduce max partition size param - experimenting with partition sizes to find value close to 16 mb limit. * Validation (2/10) - Pushed script to it's own repo - Reviews from Christophe on tcwg-buildapp job * Public Holidays (4/10) == Next Week == - Continue ongoing tasks

9 years, 4 months

1
0
0 0

[ACTIVITY]

by Renato Golin

== Progress == * Support (2/10) - Investigating a bit more PR16275, need some bigger changes in Clang/LLVM * Background (6/10) - Code review, meetings, discussions, general support, etc. - Planning for a bigger team (git, Jenkins, infrastructure, documentation) - Receiving new team members, planning start up tasks - Android NDK discussion, investigation Realising my activity report has been almost useless for the past month or so...

9 years, 5 months

1
0
0 0

[ACTIVITY] 20-24 March 2016

by Yao Qi

# Progress # * TCWG-532, done. [1/10] Canonicalize ARM syscall patch is committed. * TCWG-167, patch is posted for review. [4/10] Add ARM epilogue unwinder in GDB, which fixes many gdb.reverse test fails. * TCWG-545, V2 are posted. [1/10] * TCWG-547, [2/10] patches are reviewed, almost OK, but some changes are needed. * Talk with Jojo Ma. * Open tickets to install buildbot-slave on gcc compile farm for GDB buildbot setup. # Plan # * Holiday on Friday and next Monday. * TCWG-167, TCWG-545, TCWG-547. -- Yao

9 years, 5 months

1
0
0 0

[ACTIVITY] 14-18 March 2016

by kugan

== Progress == * LTO (3/10) - Read VRP algorithms * Type promotion pass (2/10) - Rebased and testing - Looking at fixing uninitilazed warning false positives * Misc (1/10) - GCC Lists - Extended validation * Public holiday (2/10) * Connect travel/recovery (2/10) == Plan == * Type promotion pass benchmarking * Perf with LTO * VRP

9 years, 5 months

1
0
0 0

[ANNOUNCE] Linaro Binary Toolchain Release GCC 5.3-2016.02 [Corrected Links]

by Ryan Arnold

The Linaro Binary Toolchain ============================ The Linaro GCC 5.3-2016.02 Release is now available. Notice: All Linaro GCC 5 series toolchain users should migrate to the latest version of the Linaro GCC 5 toolchain in order to mitigate potential security exposure to CVE-2015-7545. See the NEWS section below for details. Download release packages from: http://releases.linaro.org/components/toolchain/gcc-linaro/5.3-2016.02/ http://releases.linaro.org/components/toolchain/binaries/5.3-2016.02/ Previous snapshots and release-candidates are at: http://snapshots.linaro.org/components/toolchain/binaries/ Previous releases are at: http://releases.linaro.org/components/toolchain/binaries/ Host Requirements ================== Linaro officially supports the current and previous Ubuntu LTS releases (as of the time of this release). This does not mean that the toolchain will not work on other/older Linux distributions. See the following for the life-time of Ubuntu LTS releases. https://wiki.ubuntu.com/Releases The host system upon which the cross-compiler will run requires a minimum of glibc 2.14, because of API changes to glibc's memcpy API. https://bugs.linaro.org/show_bug.cgi?id=1869 Package Versions ================= Linaro GCC 5.3-2016.02 FSF glibc 2.21 (release/2.21) Linaro newlib 2.1.0-2014.09 (linaro_newlib-branch) Linaro binutils 2.25 (linaro_binutils-2_25-branch) FSF GDB 7.10 (gdb-7.10-branch) Linaro toolchain package git branches are hosted at: http://git.linaro.org/?a=project_list&s=toolchain%2F&btnS=Search NEWS for Linaro GCC 5.3-2016.02 ================================ * Applied fix for CVE-2015-7545 - A stack-based buffer overflow in glibc's getaddrinfo() was corrected in glibc 2.23 and backported into glibc 2.21. https://sourceware.org/ml/libc-alpha/2016-02/msg00416.html * ARMv8.1 Instruction Support - ARMv8.1 instructions support was checked into GCC and binutils. It has been backported into Linaro GCC 5.3 and Linaro binutils 2.25. * Backported -Bsymbolic-functions into Linaro binutils 2.25. * Performance related backports from Linaro GCC 5.2-2015.11, Linaro GCC 5.2-2015.12, and Linaro GCC 5.3-2016.01-1 have been included. See the following Linaro GCC snapshots: http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.2-2015.11/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2015.12/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.01-1/ Contact Linaro =============== File bugs at http://bugs.linaro.org For Linaro member support see http://support.linaro.org For Linaro community support email linaro-toolchain(a)lists.linaro.org

9 years, 5 months

1
0
0 0

[ANNOUNCE] Linaro Binary Toolchain Release GCC 5.3-2016.02

by Ryan Arnold

The Linaro Binary Toolchain ============================ The Linaro GCC 5.3-2016.02 Release is now available. Notice: All Linaro GCC 5 series toolchain users should migrate to the latest version of the Linaro GCC 5 toolchain in order to mitigate potential security exposure to CVE-2015-7545. See the NEWS section below for details. Download release packages from: http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.02/ http://snapshots.linaro.org/components/toolchain/binaries/5.3-2016.02/ Previous snapshots and release-candidates are at: http://snapshots.linaro.org/components/toolchain/binaries/ Previous releases are at: http://releases.linaro.org/components/toolchain/binaries/ Host Requirements ================== Linaro officially supports the current and previous Ubuntu LTS releases (as of the time of this release). This does not mean that the toolchain will not work on other/older Linux distributions. See the following for the life-time of Ubuntu LTS releases. https://wiki.ubuntu.com/Releases The host system upon which the cross-compiler will run requires a minimum of glibc 2.14, because of API changes to glibc's memcpy API. https://bugs.linaro.org/show_bug.cgi?id=1869 Package Versions ================= Linaro GCC 5.3-2016.02 FSF glibc 2.21 (release/2.21) Linaro newlib 2.1.0-2014.09 (linaro_newlib-branch) Linaro binutils 2.25 (linaro_binutils-2_25-branch) FSF GDB 7.10 (gdb-7.10-branch) Linaro toolchain package git branches are hosted at: http://git.linaro.org/?a=project_list&s=toolchain%2F&btnS=Search NEWS for Linaro GCC 5.3-2016.02 ================================ * Applied fix for CVE-2015-7545 - A stack-based buffer overflow in glibc's getaddrinfo() was corrected in glibc 2.23 and backported into glibc 2.21. https://sourceware.org/ml/libc-alpha/2016-02/msg00416.html * ARMv8.1 Instruction Support - ARMv8.1 instructions support was checked into GCC and binutils. It has been backported into Linaro GCC 5.3 and Linaro binutils 2.25. * Backported -Bsymbolic-functions into Linaro binutils 2.25. * Performance related backports from Linaro GCC 5.2-2015.11, Linaro GCC 5.2-2015.12, and Linaro GCC 5.3-2016.01-1 have been included. See the following Linaro GCC snapshots: http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.2-2015.11/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2015.12/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.01-1/ Contact Linaro =============== File bugs at http://bugs.linaro.org For Linaro member support see http://support.linaro.org For Linaro community support email linaro-toolchain(a)lists.linaro.org -- Ryan S. Arnold Linaro Toolchain Working Group - Engineering Manager www.linaro.org

9 years, 5 months

1
0
0 0

[ACTIVITY] 14-18 March 2016

by Christophe Lyon

== Progress == * Validation - extended validation: submitted ABE patch for discussion - noticed random results on some tests in the Cambridge lab. maybe caused by excessive load on the tester, or stdout/stderr problems - investigating how to actually separate stdout/stderr streams in dejagnu * GCC: - branch merge review for 2016.03 snapshot - AdvSIMD/Neon intrinsics tests: more cleanup, wondering about poly128_t prototypes * Misc (conf calls, meetings, emails, ....) == Next == * Validation: - more on extended validation - random tests investigation - more on stdout/stderr * GCC: - trunk monitoring, report regressions if needed - intrinsics tests cleanup

9 years, 5 months

1
0
0 0

[ACTIVITY] 14-18 March 2016

by Prathamesh Kulkarni

== This Week == * LTO (3/10) a) section anchors: - prototype patch to bind functions to global vars - looked at balanced partitioning b) chromium LTO build fails with ICE on trunk for arm-linux-gnueabihf: http://pastebin.com/sX6yKLBP c) ipa-comdat - Looked at the pass. - trying to address TODO: put symbol in it's own comdat section * Validation (1/10) - prototype job in bash. * Holidays (6/10) == Next Week == Continue ongoing tasks

9 years, 5 months

2
1
0 0

[ACTIVITY] Week 11

by Yvan Roux

== Progress == o 2016.03 Snapshot (2/10) * Reviewed pending backports * Merged FSF GCC 5 branch * Released 2016.03 snapshot o Extended validation (2/10) * Native validation deployed * Testing/Fixing Native Trigger job o GCC dev. (3/10) * Remote validation sanitizing: - continued discussion on output pattern - discuss I/O conflict patch with Rob, preparing a new patch * Bug #2125 - asm inline support * ARMv8.1 __sync builtins fix: on-going o Misc (3/10) * Various meetings == Plan == o Extended validation, DejaGNU patches, GCC ARMv8.1 builtins fix

9 years, 5 months

1
0
0 0

[ACTIVITY] Monday 14th - Friday 18th March

by Bernie Ogden

Port to microinstance - TCWG-432 [5/10] * Non-lab side of minimal trust benchmarking * More investigation of runtime anomalies * Reordered builder phases to do useful work while waiting for targets * Updated everything to work with benchmarking LAVA user (rather than running as me) Automated backport benchmarking - TCWG-352 [2/10] * Cycles of review/development/testing Controlled image builds - TCWG-360 [1/10] * More failures to get image to boot on Juno Log critical data - TCWG-349 [1/10] * Everything now logged, except where it depends on TCWG-360 Misc - [1/10] =Plan= Finish non-lab side of minimal trust benchmarking Commit backport benchmarking, review permitting Tweak microinstance in reaction to lab work More Juno image work More runtime anomaly work =Availability= Off from this Friday, back for three days from Monday 4th April Return to ARM on Thursday 7th April

9 years, 5 months

1
0
0 0

[Weekly] 14-18 March 2016

by Michael Collison

== This week == * Bugzilla 69663 - [ARM] Implement overflow arithmetic standard names (5/10) - Resolved 50% of thumb2 failures - Resolved issues with overlapping registers and not setting condition codes - Wrote compile only test cases that pass validation * TCWG-247 - Create Validation Job to run on GCC Trunk Commits (2/10) - Investigation into Python API for discovering when Jenkins builders are idle * Linaro connect recovery day (2/10) * Misc meeting (1/10) == Next week == * Bugzilla 69663 - [ARM] Implement overflow arithmetic standard names - Resolve remaining thumb2 issues * TCWG-247 - Create prototype implementation

9 years, 5 months

1
0
0 0

[ACTIVITY]

by Renato Golin

= Progress == * Day off (2/10) - After Connect, recuperating, jet lagging * EuroLLVM (6/10) - Flying Wed to Barcelona, attending conference - Back on Saturday * Background (2/10) - Code review, meetings, discussions, general support, etc. - Planning for a bigger team (git, Jenkins, infrastructure)

9 years, 5 months

1
0
0 0

[ACTIVITY] 14 March -- 18 March

by Yao Qi

* Sick on Monday [2/10] # Progress # * AArch64/ARM linux syscall for process record. [2/10] TCWG-532 ARM patch (fixing the register for syscall arg pass) is committed. Canonicalize ARM syscall patch is posted for review. * Support range stepping on arm-linux. [4/10] TCWG-545 Preparatory patches fixing bugs when "single step the instruction branch to itself" are being reviewed. Pedro thinks my patches may not work in some rare cases, and I spend some time writing the case and prove it won't happen. * Misc [2/10] ** file expense, ** upstream patch review, # Plan # * TCWG-532 * TCWG-545 -- Yao

9 years, 5 months

1
0
0 0

[ANNOUNCE] Linaro GCC 5 2016.03 snapshot

by Yvan Roux

The Linaro Toolchain Working Group (TCWG) is pleased to announce the 2016.03 snapshot of the Linaro GCC 5 source package. This monthly snapshot[1] is based on FSF GCC 5.3+svn234210 and includes performance improvements and bug fixes backported from mainline GCC. This snapshot contents will be part of the 2016.05 stable [1] quarterly release. This snapshot tarball is available on: http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.03/ Interesting changes in this GCC source package snapshot include: * Updates to GCC 5.3+svn234210 * Backport of [Bugfix] [AArch64] [Linaro #1994] Disable pcrelative_literal_loads with fix-cortex-a53-843419 * Backport of [Bugfix] [AArch64] [Linaro #2123] Fix dependency of gcc-plugin.h * Backport of [Bugfix] [AArch32] PR target/62554 target/69610 Fix for ARMv3 * Backport of [Bugfix] [AArch32] PR target/69161: Don't ignore mode when matching comparison operator in cstore-like patterns * Backport of [AArch32] Enable instruction fusion of AES instructions on ARM for Cortex-A53 and Cortex-A57 * Backport of [AArch64] Add missing return in aarch64_internal_mov_immediate * Backport of [AArch64] Enable instruction fusion of dependent AESE; AESMC and AESD; AESIMC pairs * Backport of [AArch64] Fix installed plugin headers for aarch64, m68k and c6x * Backport of [AArch64] GCC 6 regression in vector performance. - Fix vector initialization to happen with lane load instructions * Backport of [AArch64] Restrict 16-bit sqrdml{sa}h instructions to FP_LO_REGS * Backport of [Testsuite] [AArch64] add check for aarch64 in check_effective_target_section_anchors * Backport of [Testsuite] Print markers to stderr to avoid races with sanitizer output * Backport of [Misc] Fix ChangeLog for 233518 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 bugzilla against GCC product: http://bugs.linaro.org/enter_bug.cgi?product=GCC * Interested in commercial support? inquire at "Linaro support": mailto:support@linaro.org [1]. Stable source package releases are defined as releases where the full Linaro Toolchain validation plan is executed. [2]. Source package snapshots are defined when the compiler is only put through unit-testing and full validation is not performed.

9 years, 5 months

1
0
0 0

[ACTIVITY] 7-11 March 2016

by Christophe Lyon

== Progress == * Connect: attended remotely - internal TCWG sessions - Extended validation: support more flexibility in ABE * GCC - Fixed bugs 2123, 1994 - Neon intrinsics tests cleanup - A few backports * Misc (conf calls, meetings, emails, ...) == Next == * Extended validation * GCC bug fixing

9 years, 5 months

1
0
0 0

[ACTIVITY] Week 10

by Yvan Roux

== Progress == o BKK16 remote (5/10) * Followed TCWG sessions * Extended validation: - worked with Kugan - implemented job for native validation o GCC dev. (4/10) * Remote validation sanitizing: - iterate on the output pattern fix - testing a fix for stderr/stdin ordering issue * Gave some support on __sync builtins, preparing a fix for armv8.1 o Misc (1/10) * Various meetings == Plan == o GCC 5 branch merge, and 2016.03 snapshot o Continue on-going tasks

9 years, 5 months

1
0
0 0

[ACTIVITY] 29th Februrary - 11th March

by Bernie Ogden

Port to microinstance - TCWG-432 [17/10] * Investigating difference between LAVA and 'desktop Juno' runtimes ** Some of this was down to piles of /dev/console output - redirecting to file improved SPEC build time by 75%! ** Some cases make sense, others remain unexplained ** Might just go away if we update the Juno image * Wrote up how to do benchmarking for minimal-trust cases ** Needs both lab and development work * Merged another large tranche of changes back to benchmarking branch ** Microinstance more or less functional, main instance benchmarking seems unbroken ** But some more tweaks to make as Lab work happens * Prepared backport benchmarking for merge Misc [3/10] =Plan= * Submit backport benchmarking for review * Tweak uinstance in reaction to lab work * Implement the non-lab side of minimal-trust benchmarking * Return to looking at Juno image generation * Look some more at LAVA/desktop runtime differences * Implement small improvements, if time

9 years, 5 months

1
0
0 0

[Weekly] 07-11 March 2016

by Michael Collison

== This week == * Bugzilla 69663 - [ARM] Implement overflow arithmetic standard names (3/10) - Resolved thumb2 failures - Negdi2 was not generating instruction to set condition codes * Bugzilla 70008 - [ARM] Reverse subtract with carry can be generated in thumb2 mode (1/10) - Created new patch using new predicate that matches arm and thumb2 constraints - Received approval to GCC 7 stage 1 * Bugzilla 70014 - [ARM] Predicate does not match constraint (*subsi3_carryin_const) (1/10) - Fix checked into trunk * Linaro Connect meetings (5/10) == Next week == * Bugzilla 69663 - [ARM] Implement overflow arithmetic standard names - Create compile only test cases and re-run validation testing - Post new patch upstream

9 years, 5 months

1
0
0 0

Updating LLVM on Debian/Ubuntu

by Renato Golin

Hey, Regarding the GCC ABI 5 issue, I was wondering what's the policy behind updating packages on stable updates for both Debian and Ubuntu. Our time frame is a bit constrained, and we definitely will have to take some hard decisions in the next six months, so I'd like to understand everything that is at stake before I have my own opinion. LLVM has a 6 month major cycle, releasing around February / August. Major releases are allowed to break the ABI. Major breakages need one release warning period. Ubuntu has a 6 month release cycle, around April / October. IIUC, major releases are allowed to have new versions of packages, but updates for the next few years have to keep within the same major release. Debian has a -1 years release cycle (heh), and has the same major / minor policy, which makes it a lot harder to update major versions. However, I believe unstable is still not closed, nor will be in August this year, so updating to LLVM 3.9 will not be a problem, but it will mean users will have to wait a bit more to get a working LLVM. The time frame is then: 3.8.0 released March (without the fix) Ubuntu X released April 3.9.0 releases August (hopefully with a fix) Ubuntu X+1 released October Debian freezes ?? LLVM 3.8.1 ?? If we don't back-port GCC ABI 5 into 3.8.1, Ubuntu users will not have the fix ever, unless you *can* update to 3.9.0 in August. Ubuntu X+1 will be fine using 3.9, as will Debian after August, unless you guys freeze before that. I believe both Debian and Ubuntu have a trunk-based LLVM package for experimental use only, and it would be bad, but not completely broken, to recommend users to use that meanwhile. If Debian freezes *before* 3.9.0 is out, or if Ubuntu can't update to 3.9.0 on April's release, then we'll have a strong reason to back-port the change to 3.8.x. If not, even though it will be uncomfortable for users until August, the argument is not that strong and will be hard to get it through. Any comments? Ideas? Does any of that make sense? cheers, --renato

9 years, 5 months

2
2
0 0

Some questions about the gcc __sync intrinsics

by Edward Nevill

Hi, I have been comparing the stock gcc 5.2 and the Linaro 5.2 (Linaro GCC 5.2-2015.11-1) and have noticed a difference with the __sync intrinsics. Here is the simple test case --- cut here --- int add_int(int add_value, int *dest) { return __sync_add_and_fetch(dest, add_value); } --- cut here --- Compiling with the stock gcc 5.2 (-S -O3) I get --------- add_int: .L2: ldaxr w2, [x1] add w2, w2, w0 stlxr w3, w2, [x1] cbnz w3, .L2 mov w0, w2 ret --------- Wheras with Linaro gcc 5.2 I get --------- add_int: .L2: ldxr w2, [x1] add w2, w2, w0 stlxr w3, w2, [x1] cbnz w3, .L2 dmb ish mov w0, w2 ret --------- Why the extra (unnecessary?) memory barrier? Also, is it worthwhile putting a prfm before the ldaxr. EG add_int: prfm pst1strm, [x1] .L2: ldaxr w2, [x1] See the following thread http://lists.infradead.org/pipermail/linux-arm-kernel/2015-July/355996.html All the best, Ed

9 years, 5 months

3
6
0 0

FreeBSD + LLD Update

by Renato Golin

FYI, http://lists.llvm.org/pipermail/llvm-dev/2016-March/096449.html cheers, --renato

9 years, 5 months

1
0
0 0

[ACTIVITY] Week 09

by Yvan Roux

== Progress == o GCC dev. (7/10) * Remote validation sanitizing: - fixed last issues in dejagnu patch and submitted it uptsream - 2 more cleanup/fix dejagnu patches submitted and merged upstream - proposed a fix/workaround for the output pattern issues (>400 failures removed with this patch) o Misc (3/10) * Various meetings * internal discussions == Plan == o Try to follow connect remotely o Extended validation work

9 years, 5 months

1
0
0 0

[ACTIVITY] 29 February-4 March 2016

by Christophe Lyon

== Progress == * GCC bugs: - #2073 tried to reproduce it with a manually-built toolchain. No luck * GCC validation: - added support to choose simulated cpu (different from --with-cpu) * GCC: - completing Neon intrinsics tests, to prepare cleanup * Validation: - small improvements * Misc (conf calls, meetings, emails, ...) == Next == Remote Connect

9 years, 5 months

1
0
0 0

[ACTIVITY]

by Renato Golin

== Progress == * Support (5/10) - Working on PR17193 - Continue review on D17141 * Background (5/10) - Code review, meetings, discussions, general support, etc. - Connect preparations - GCC ABI 5 discussions - Assessing Swift calling convention impact ARM back-end - Interviews

9 years, 5 months

1
0
0 0

[ACTIVITY] 29 Feb -- 04 Mar

by Yao Qi

# Progress # * TCWG-545, Handle "branch-to-self" instruction in single stepping. [5/10] Patches are posted upstream for review. * TCWG-532, one patch is committed and one patch is posted for review. [2/10] * Tweak ARM process record. [2/10] Two patches are pushed in. Many test fails are fixed. * FSF patches review. [1/10]. # Plan # * Linaro Connect. -- Yao

9 years, 5 months

1
0
0 0

gcc 5.2 code quality

by Edward Nevill

Hi, I have just switched to gcc 5.2 from 4.9.2 and the code quality does seem to have improved significantly. For example, it now seems much better at using ldp/stp and it seems to has stopped gratuitous use of the SIMD registers. However, I still have a few whinges:-) See attached copy.c / copy.s (This is a performance critical function from OpenJDK) pd_disjoint_words: cmp x2, 8 <<< (1) sub sp, sp, #64 <<< (2) bhi .L2 cmp w2, 8 <<< (1) bls .L15 .L2: add sp, sp, 64 <<< (2) (1) If count as a 64 bit unsigned is <= 8 then it is probably still <= 8 as a 32 bit unsigned. (2) Nowhere in the function does it store anything on the stack, so why drop and restore the stack every time. Also, minor quibble in the disass, why does sub use #64 whereas add uses just '64' (appreciate this is probably binutils, not gcc). .L15: adrp x3, .L4 add x3, x3, :lo12:.L4 ldrb w2, [x3,w2,uxtw] <<< (3) adr x3, .Lrtx4 add x2, x3, w2, sxtb #2 br x2 (3) Why use a byte table, this is not some sort of embedded system. Use a word table and this becomes. .L15: adrp x3, .L4 add x3, x3, :lo12:.L4 ldr x2, [x3, x2, lsl #3] br x2 An aligned word load takes exactly the same time as a byte load and we save the faffing about calculating the address. .L10: ldp x6, x7, [x0] ldp x4, x5, [x0, 16] ldp x2, x3, [x0, 32] <<< (4) stp x2, x3, [x1, 32] <<< (4) stp x6, x7, [x1] stp x4, x5, [x1, 16] (4) Seems to be something wrong with the load scheduler here? Why not move the stp x2, x3 to the end. It does this repeatedly. Unfortunately as this function is performance critical it means I will probably end up doing it in inline assembler which is time consuming, error prone and non portable. * Whinge mode off Ed

9 years, 5 months

6
9
0 0

[ANNOUNCE] Linaro Binary Toolchain Release-Candidate GCC 5.3-2016.02-rc1

by Ryan Arnold

The Linaro Binary Toolchain ==================================== Release-Candidate Linaro GCC 5.3-2016.02-rc1 is now available. Notice: All Linaro GCC 5 series toolchain users should migrate to the latest version of the Linaro GCC 5 toolchain in order to mitigate potential security exposure to CVE-2015-7545. See the NEWS section below for details. Download release-candidate packages from: http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.02-rc1/ http://snapshots.linaro.org/components/toolchain/binaries/5.3-2016.02-rc1/ Previous snapshots and release-candidates are at: http://snapshots.linaro.org/components/toolchain/binaries/ Previous releases are at: http://releases.linaro.org/components/toolchain/binaries/ Host Requirements ================== Linaro officially supports the current and previous Ubuntu LTS releases (as of the time of this release). This does not mean that the toolchain will not work on other/older Linux distributions. See the following for the life-time of Ubuntu LTS releases. https://wiki.ubuntu.com/Releases The host system upon which the cross-compiler will run requires a minimum of glibc 2.14, because of API changes to glibc's memcpy API. https://bugs.linaro.org/show_bug.cgi?id=1869 Package Versions ================= Linaro GCC 5.3-2016.02-rc1 FSF glibc 2.21 (release/2.21) Linaro newlib 2.1.0-2014.09 (linaro_newlib-branch) Linaro binutils 2.25 (linaro_binutils-2_25-branch) FSF GDB 7.10 (gdb-7.10-branch) Linaro toolchain package git branches are hosted at: http://git.linaro.org/?a=project_list&s=toolchain%2F&btnS=Search NEWS for Linaro GCC 5.3-2016.02-rc1 ==================================== * Applied fix for CVE-2015-7545 - A stack-based buffer overflow in glibc's getaddrinfo() was corrected in glibc 2.23 and backported into glibc 2.21. https://sourceware.org/ml/libc-alpha/2016-02/msg00416.html * ARMv8.1 Instruction Support - ARMv8.1 instructions support was checked into GCC and binutils. It has been backported into Linaro GCC 5.3 and Linaro binutils 2.25. * Backported -Bsymbolic-functions into Linaro binutils 2.25. * Performance related backports from Linaro GCC 5.2-2015.11, Linaro GCC 5.2-2015.12, and Linaro GCC 5.3-2016.01-1 have been included. See the following Linaro GCC snapshots: http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.2-2015.11/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2015.12/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.01-1/ Contact Linaro =============== File bugs at http://bugs.linaro.org For Linaro member support see http://support.linaro.org For Linaro community support email linaro-toolchain(a)lists.linaro.org -- Ryan S. Arnold Linaro Toolchain Working Group - Engineering Manager www.linaro.org

9 years, 5 months

1
0
0 0

[ACTIVITY] 22nd - 26th February

by kugan

== Progress == - BUGS (6/10) * Posted patches for the bugs https://gcc.gnu.org/ml/gcc-patches/2016-02/msg01974.html https://gcc.gnu.org/ml/gcc-patches/2016-02/msg01927.html https://gcc.gnu.org/ml/gcc-patches/2016-02/msg01905.html * Addressed review comments - Connect presentation (2/10) - Misc (2/10) * gcc/bug list * Meetings == Plan == * LTO * bugs

9 years, 5 months

1
0
0 0

[ACTIVITY] Week 08

by Yvan Roux

== Progress == o GCC dev. (7/10) * Remote validation sanitizing: - Implemented and tested a pure dejagnu fix (the actual implementation works fine for GCC but might be an issue in a different context, a cleaner fix almost done) - Found a latent issue in GCC profiling test harness * ARM and AArch64 backends LRA cleanup: - Looked at the remaining artifacts, will prepare a patch for GCC 7 o Misc (3/10) * Various meetings * internal discussions == Plan == o Finalize and submit dejagnu fix

9 years, 5 months

1
0
0 0

[ACTIVITY] 22nd - 26th February

by Bernie Ogden

Port to microinstance - TCWG-432 [7/10] * Merged last few months of development back to benchmarking branch * Restored support for multiple targets per builder * Updated builder landed, altered jobs to work with it ** Removed assumption that host filesystem is non-persistent ** Stacked up test runs for the weekend Transfer secret management to LAVA [1/10] * LAVA jobs now use a within-LAVA key to access sources Misc [2/10] * Unsuccessful fiddling with heat-monitoring tools on Juno * Usual background of mail and meetings =Plan= * Fallout from weekend test runs ** Some failure is going on, need to investigate * Update docs and Jenkins configs w.r.t. last week's activity * Further investigation on a couple of LAVA issues that are causing me pain ** Un-deserializable bundles ** Inaccessible image reports * Continue assessing target stability/looking at inconsistent results

9 years, 5 months

1
0
0 0

[Weekly] 22-26 February 2016

by Michael Collison

== This week == * Bugzilla 69663 - [ARM] Implement overflow arithmetic standard names (6/10) - Tested and posted SImode and DImode patch upstream - Feedback recommended supporting thumb2 in addition to arm architectures - Patch to support thumb2 fails on all thumb architectures; investigating failures * Bugzilla 70008 - [ARM] Reverse subtract with carry can be generated in thumb2 mode (2/10) - Created new bug, developed and successfully tested patch - Fix posted upstream * Bugzilla 70014 - [ARM] Predicate does not match constraint (*subsi3_carryin_const) (1/10) - Created new bug and patch * Misc (1/10) == Next week == * Bugzilla 69663 - Cleanup by merging patterns using mode iterators, submit upstream * Bugzilla 70008 - Respond to upstream comments as appropriate * Bugzilla 70014 - Post patch and respond to upstream comments * Travel to Linaro Connect beginning March 3rd

9 years, 5 months

1
0
0 0

[ACTIVITY] 22-26 Feb 2016

by Prathamesh Kulkarni

== This Week == * LTO (6/10) - TCWG 528: a) reduced test-case for the case when decl node gets visited multiple times b) updated patch not to walk artificial record decls (typeinfo objects) as per Richard's suggestion. submitted upstream, waiting for review. - benchmarking: Aarch64 SPEC2006-int benchmarks complete - looked at pr57703 - Slides * setting up perf on chromebook (2/10) - perf doc - got perf running on chromebook by manually building it and set of (clumsy) workarounds. - perf annotate shows no output and perf stat shows "not supported" for almost all entires except "page faults" - will give a try to dual boot chrubuntu on chromebook * half-day sick leave (1/10) - doctor's appointment for eye inflammation * Misc (1/10) - Meetings == Next Week == - LTO - tcwg-310 - look at jenkins tutorial in collaborate wiki

9 years, 5 months

1
0
0 0

[ACTIVITY]

by Renato Golin

== Progress == * Support (4/10) - Updating patch D17141 for Darwin, resubmitting, discussions. - Understanding PR21778, may need changes to SLP - Benchmarking some scheduler choices for A17 * Release (1/10) - 3.8.0 RC3 validation * Background (5/10) - Code review, meetings, discussions, general support, etc. - Sifting through CVs, interviews, etc.

9 years, 5 months

1
0
0 0

[ACTIVITY] 22-26 Feb 2016

by Yao Qi

# Progress # * Support range stepping on arm-linux. TCWG-518. [5/10] Post patch series about "the thread is stepping over breakpoint but it spawns child thread". The fix is OK but the test case changes are being reviewed. The more I test my range stepping patches, the more existing bugs I find. Looking at the bug "software single step the instruction branch to self." * AArch64 linux syscall for record/replay. TCWG-532. [1/10] Patch is out for review. * Fix some ARM reverse debugging bugs. TCWG-183. [1/10] Patch is pushed in. The original implementation wasn't carefully reviewed, so I am sure there are bugs somewhere else. * Patch review on arm tracepoint support. [1/10] One patch is approved but I insist that another patch should be done in generic part instead of ARM specific part, but the author wants do it in ARM specific part because he things it is simpler. * Misc [2/10] ** Go through the Linux kernel awareness GDB patches quickly, the first reaction is "split your patch, please". ** Go to London to collect my passport. # Plan # * Support range stepping on arm-linux. TCWG-518. * TCWG-167, TCWG-532. * Prepare for the Linaro Connect travel. -- Yao

9 years, 5 months

1
0
0 0

[ACTIVITY] 22-26 February 2016

by Christophe Lyon

Short week, off Mon-Wed == Progress == * Validation - testing timeout increase * Connect preparation - discussions on extended validation * GCC - looking at bug #2073 (GCC crash under Windows) - target attributes backport * Misc (conf-calls, meetings, emails, ....) == Next == * Connect preparation * GCC bugs

9 years, 5 months

1
0
0 0

Static arm-gcc

by $rik＠nth

Hi All, Does linaro distributes arm-gcc as a pre-built static tool chain distribution? If yes, where can i download them from. Please point me some location from where i can download. -- Thanks & Regards, M.Srikanth Kumar.

9 years, 6 months

2
2
0 0

[ACTIVITY] 15th - 19th Februrary

by Bernie Ogden

Bug with compiler flag handling - (no ticket) [2/10] * Coremark-Pro was ignoring compiler flags * Fixed that, made flag handling consistent across all benchmarks Release benchmarking via Jenkins - TCWG-348 [1/10] * Seems to work with test workload Port to microinstance - TCG-432 [3/10] * Looked at some inconsistent results * Worried that one of the Junos may be sick, but unproven for now Backport benchmarking via Jenkins - TCWG-352 [1/10] * Finished 'general benchmarking' job * Switched backport job to build/test cross-compilers * Recent backport results bundles are corrupted, unable to work out why Document benchmarking infrastructure - TCWG-496 [1/10] * Documented Jenkins interface Misc [2/10] =Plan= If updated builder becomes available, convert uinstance job to use it Continue assessing target stability/looking at inconsistent results Rework LAVA scripts to permit multiple targets per builder

9 years, 6 months

1
0
0 0

[Weekly] 15-19 February 2016

by Michael Collison

== This week == * Bugzilla 69663 - [ARM] Implement overflow arithmetic standard names (4/10) - Successfully tested SImode add, sub, and neg overflow patterns - Resolved DImode addv and subv code generation issues. - Minor cleanup work remains before posting upstream * Bugzilla 69008 - gcc emits unneeded memory access when passing trivial structs by value (ARM) (3/10) - Restarted by investigating dead store elimination pass * Misc (1/10) * Expedited passport (2/10) == Next week == * Bugzilla 69663 - Cleanup by merging patterns using mode iterators, submit upstream * Bugzilla 69008 - Continue investigation

9 years, 6 months

1
0
0 0

[fido][meta-linaro-toolchain] arm-none-eabi-4.8-2014.04

by Xi Zhou Zhou

Hi all, I download the pre-built toolchain for one of our armv6 board. https://releases.linaro.org/14.04/components/toolchain/binaries/gcc-linaro-… After plug it into Yocto as an external toolchain, it failed to install it correctly. ../meta-linaro/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/ external-linaro-toolchain.bb, do_install | DEBUG: Executing shell function do_install | cp: cannot stat `/opt/gcc-linaro-arm-none-eabi-4.8-2014.04_linux/arm-none-eabi/libc/lib/*': No such file or directory Any suggestion? Thanks, Joel

9 years, 6 months

2
1
0 0

[ACTIVITY] 15-19 Feb 2016

by Prathamesh Kulkarni

== This Week == * LTO (5/10) - TCWG-528: a) addressed Richard's comments. b) investigating timeout with my patch for g++.dg/torture/pr31863.C c) using hash_map to prevent decl from getting visited more than once prevents the issue d) patch: http://people.linaro.org/~prathamesh.kulkarni/increase-struct-align.diff - Slides: mostly prepared, few tidbits (and demos) remaining - Benchmarking: couple more failures due to my silly mistakes, now in progress. * TCWG-310 (1/10) - started to look at loop peeling with perf * Public Holiday (2/10) - Shiv Jayanti * Misc (2/10) - Meetings - Committed r233426 - Looked at PR69766 caused due to r232622 == Next Week == - LTO: TCWG-528, benchmarking, slides - TCWG-310

9 years, 6 months

1
0
0 0

[ACTIVITY] 15 - 19 February 2016

by Yao Qi

# Progress # * Support range stepping on arm-linux. TCWG-518. [4/10] My patches causes some regressions but my patches just expose the existing problem in GDBserver. Fix them and post patches upstream. * Linaro connect. [2/10] Go to London for visa application. * GDB 7.11 release. No issues from my side. The tentative date of release is Feb 26th. * Fix GDB reverse debugging tests failures. ** Add more test cases, TCWG-183/TCWG-174. [2/10] ** Fix syscall handling in reverse debugging on ARM and AArch64. TCWG-532/TCWG-167. [2/10] # Plan # * Support range stepping on arm-linux. Continue. * Fix GDB reverse debugging tests failures. Continue. * Review upstream patches. * Go to London to collect my passport. -- Yao

9 years, 6 months

1
0
0 0

[ACTIVITY] 15-19 February 2016

by Christophe Lyon

== Progress == * Validation - AArch64 bare metal validation fixed. Patches waiting approval - noticed a few failures caused by timeouts and failure to download testcases. Maybe we are causing too much load on the builders/testers * Connect preparation - thoughts on extended validation * GCC - upstream monitoring, reported a couple a of regressions - a few backports - target attributes backport. Still having problems with our branch * Misc (conf calls, meetings, emails, ....) == Next == Holidays most of next week

9 years, 6 months

1
0
0 0

setting loop buffer size in the gcc (aarch64)

by Virendra Kumar Pathak

Hi Toolchain Group, I am trying to study the effect of loop buffer size on loop unrolling & the way gcc (aarch64) handles this. To my understanding, Loop Buffer is like i-cache which contains pre-decoded instruction that can be re-used if branch instruction loopbacks to an instruction which is still present in the buffer. For example, in Intel’s Nehalem loop buffer size is 28 u-ops. In LLVM compiler, it seems LoopMicroOpBufferSize is for the same purpose. However, I could not find any parameter/variable inside config/aarch64 representing loop buffer size. I am using Linaro gcc 5.2.1 [Question] 1. Is there any example inside aarch64 (or in general) which uses the loop buffer size in loop unrolling decision? If yes, could you please mention the relevant files or code section? 2. Otherwise any guidance/input on adding this support in aarch64 backend assuming architecture has the loop buffer support. [My Experiments/Code Browsing] I have collected following information from code browsing. Please correct if I missed or misunderstood something. TARGET_LOOP_UNROLL_ADJUST - This target hook return the number of times a loop can be unrolled. This can be used to handle the architecture constraint such number of memory references inside a loop e.g. ix86_loop_unroll_adjust() & s390_loop_unroll_adjust(). On the same note, can this be used to handle loop buffer size too? Without above hook, in loop-unroll.c parameters like PARAM_MAX_UNROLLED_INSNS (default 200), PARAM_MAX_AVERAGE_UNROLLED_INSNS (default 80) decides the unrolling factor. e.g. nunroll = PARAM_VALUE (PARAM_MAX_UNROLLED_INSNS) / loop->ninsns; In config/aarch64.c, I found align_loops variable in aarch64_override_options_after_change() function. I guess this an alignment done before starting the loop header in the executable. This should not play any role in loop unrolling. Right? So any guidance on how we can instruct aarch64 backend to utilize loop buffer size in deciding the loop unrolling factor? Thanks in advance for your time. -- with regards, Virendra Kumar Pathak

9 years, 6 months

3
2
0 0

[ACTIVITY] 8 - 12 February 2016

by Omair Javaid

== Progress == LLDB development -- Handling aggregate types return values on arm-linux-gnueabihf ABI. Patch review and committed upstream. [TCWG-228] [1/10] -- Debugging of stepping issues on chromebook (arm hard float ABI) [TCWG-230] [2/10] -- Progress on vector return values and aggregate types return values with vector elements. [TCWG-531] [2/10] -- Started work on complex return values and aggregate types return values with vector elements. [TCWG-531] [2/10] -- Started writing test cases handling complex and vector return values and aggregate types return values with vector and complex elements. [TCWG-531] [2/10] Miscellaneous [1/10] -- Meetings, emails, discussions etc. == Plan == LLDB development -- Finish work on complex return values and aggregate types return values with vector elements. [TCWG-531] -- Finish work on vector return values and aggregate types return values with vector elements. [TCWG-531] -- Finish work on test cases handling complex and vector return values. [TCWG-531]

9 years, 6 months

1
0
0 0

[ACTIVITY] 8th - 12th February

by Bernie Ogden

Port to microinstance - TCWG-432 [2/10] * Better reporting/error trapping in dispatch scripts * Some back and forth with Lab about builder implementation * Started assessing target stability * Fixed a few bugs in reporting/bundle generation Document benchmarking infrastructure - TCWG-496 [2/10] * All done apart from Jenkins interface * Need to finish Jenkins interface first... Generate graphs for benchmarking - TCWG-268 [1/10] * Generate a bunch of filters and charts to track Coremark-Pro * Wrote up what I learned about LAVA's reporting interface EEMBC benchmarks - (no ticket) [2/10] * Checked over what we had, decided it was probably complete * Imported to our repos * Wrote up what I know about this * Moved Coremark-Pro into its own repo ** Broke some code that had worked by coincidence ** Fixed it Misc * Usual meetings/mail/etc * Some fun with what turned out to be a known bug in the linaro-media-create now used in main LAVA instance * Educated guess as to why Jenkins-triggered jobs produced no bundle ** Raised a ticket ** Think I know how to fix on my side =Plan= If updated builder becomes available, convert uinstance jobs to use it Test release benchmark job Finish backport benchmarking Document Jenkins interface Assess target stability More image reports in microinstance

9 years, 6 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain