linaro-toolchain

linaro-toolchain@lists.linaro.org

6 participants
5661 discussions

[ACTIVITY] 30 October-3 November 2017

by Christophe Lyon

Short week (off Wed/Thu/Fri) == Progress == * GCC - FDPIC: looking at patch stacks * GCC upstream validation: - got feedback from upstream about qemu and asan interaction since recent merge: need to disable LSAN on arm. - using qemu-2.7 again enables to workaround the timeout issues observed last week - worked on improving timeout handling - restarted validations, but.... - validations on-hold since Nov 1st because of an ST-internal infrastructure problem * Infrastructure: * misc (conf-calls, meetings, emails, ....) == Next == * GCC upstream validation * GCC/ubsan * GCC/FDPIC

8 years

[ACTIVITY] Week 44

by Yvan Roux

* 3 days off == Progress == o Linaro GCC/Validation o LLVM * Continue ramp-up * Upstream bug 32999: - Reworked the fix and validate it - Ready to be submitted upstream * Start to look at sign-extension elimination status o Misc == Plan == o Release handover (5 release, 6 and 7 RCs) o LLVM tasks (Bug 32999, sign-extension)

8 years

[ACTIVITY] Oct 27 -- Nov 03

by Yao Qi

# Progress # * TCWG-1040, [6/10] Update my patches to remove the last use of MAX_REGISTER_SIZE. Commit clean up and refactor patches. Find more clean up patches in my tree. Keep upstreaming them. The design and implementation of removing MAX_REGISTER_SIZE becomes more and more clear. * TCWG-1125, [2/10] ARMv8 tagged address support in GDB. v2 patches were posted. No comments yet. * aarch64: PR 19806: watchpoints: false negatives + PR 20207 contiguous ones. Patch review. [1/10] * Think about the TODOs for GDB ILP32 support, write them down, and send it to Maxim. [1/10] # Plan # * TCWG-1040, TCWG-1125. -- Yao Qi

8 years

aarch64 toolchain support NEON and vfp features

by Joy Deng

Hi , I am a SW engineer that use Linaro-toolchain to build images, Recently, I encounter some issue about enable NEON features on ARMv8 processor platform. I cat cpuinfo, can not find neon and vfp feature enable in list, the image was build with aarch-64 toolchian; While, the image built by armv7l toolchain can list "neon and vfp" in cpuinfo. I want to verify from your side, 1. if the toolchain of aarch64 version already enable" neon and vfp " in default, Because I do not find some build items that related with "neon", 2. If not supported defaultly, can you give some suggestion to enable it. Thanks & B.R. Joy Deng

8 years

[ACTIVITY] 23 October - 27 October 2017

by Prathamesh Kulkarni

== This Week == * TCWG-1005 (4/10) - Iteration on upstream feedback and validated patch - Committed to trunk in r254140. * Reverse of TCWG-1253 transform (3/10) - Adding reverse transform for div pattern in expand * TCWG-1234 (2/10) - Experimenting with "unhoisting" approach * Misc (1/10) - Meetings == Next Week == - Continue ongoing and backlog tasks from JIRA - Go through IPA mod/ref paper

8 years

[ACTIVITY] Week 43

by Yvan Roux

* One day off == Progress == o Linaro GCC/Validation * Releases handover - GCC 5.5 source snapshot and RC1 deployed - GCC 6 and 7 RCs under construction o LLVM * Continue ramp-up * Upstream bug 32999: - Validating a fix o Misc * Various meetings and discussions. == Plan == o Continue release handover and LLVM ramp-up

8 years

[ACTIVITY] 23-27 October 2017

by Christophe Lyon

== Progress == * GCC - FDPIC: started reading docs and looking at patches - Neon intrinsics PR71233: duplicates will be removed from the next doc update * GCC upstream validation: - since ubsan merge with upstream, validation of arm targets is now broken. Switching back to qemu-2.7 seems to avoid qemu deadlocks, but there are still new asan test failures after the merge. - reduced the dejagnu timeout to avoid global 'make check' timeouts, but this caused some testcases to become zombies, in turn causing problems in the ST compute farm. - validation on-hold until next so that I can experiment a bit more with workarounds - reported another qemu bug - reported a couple of regressions/breakages in binutils * Infrastructure: * misc (conf-calls, meetings, emails, ....) == Next == * GCC upstream validation * GCC/ubsan * GCC/FDPIC * Short week (off Wed/Thu/Fri)

8 years

[ACTIVITY] Oct 23 - 27

by Yao Qi

* TCWG-1040, [4/10] Update my patches to remove the last use of MAX_REGISTER_SIZE. Post the clean up and refactor patches. * TCWG-1125, [4/10] ARMv8 tagged address support in GDB. v2 patches are posted. Take care of breakpoint and watchpoint on tagged address carefully. * ILP32 GDB branch. [1/10] Branch is created! Done. * Misc, meeting, [1/10] # Plan # * Update my patches to remove the last use of MAX_REGISTER_SIZE. * GDB flexible target description conversion. Upstream patches. -- Yao Qi

8 years

[ANNOUNCE] Linaro Binary Toolchain Release-Candidate GCC 5.5-2017.10-rc1

by Mark Murray

[ANNOUNCE] Linaro Binary Toolchain Release-Candidate GCC 5.5-2017.10-rc1 The Linaro Binary Toolchain ============================ The Linaro GCC 5.5-2017.10-rc1 Release-Candidate 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-7547. See the NEWS section below for details. Download release-candidate packages from: (sources) http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.5-2017.10-rc1/ (binaries) http://snapshots.linaro.org/components/toolchain/binaries/5.5-2017.10-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/ A description of the arm and AArch64 target triples can be found at: https://collaborate.linaro.org/display/TCWGPUB/ARM+and+AArch64+Target+Tripl… 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.5-2017.10-rc1 http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.5-2017.10-rc1/ Linaro glibc 2.21 (linaro/2.21) https://lists.gnu.org/archive/html/info-gnu/2015-02/msg00001.html Linaro newlib 2.1.0-2014.09 (linaro_newlib-branch) https://sourceware.org/ml/newlib/2013/msg01128.html Linaro binutils 2.25 (linaro_binutils-2_25-branch) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=bin… FSF GDB 7.12 (gdb-7.12-branch) https://lists.gnu.org/archive/html/info-gnu/2016-10/msg00007.html Linaro toolchain package git branches are hosted at: http://git.linaro.org/toolchain NEWS for GCC 5 (as of Linaro GCC 5.5-2017.10-rc1) ================================================== * Include GCC fix for Linaro bugzilla #2575: ICE: declaration and definition of function with __attribute__((target("thumb"))) and inlined assembler, with debug symbols enabled https://bugs.linaro.org/show_bug.cgi?id=2575 * Include GCC fix for Linaro bugzilla #2575: Internal compiler error using -mtune=cortex-a57.cortex-a53. https://bugs.linaro.org/show_bug.cgi?id=2785 * The soft-float targeted toolchains have now been configured to generate code using -mfloat-abi=soft. This makes arm-linux-gnueabi and armeb-linux-gnueabi toolchains use the “soft” FP ABI instead of “softfp”. Historically, TCWG’s toolchains provided both “soft” and “softfp” multilibs, but when switching from crosstool-ng to cbuildv2/abe (which support a single multilib) “softfp” multilib was choosen. Using “-mfloat-abi=soft” is a better choice for a gnueabi toolchain, since it doesn’t require cores to have a floating-point unit. This change should not break compatibility for toolchain users since the ABI will stay the same. The compiler and glibc libraries will not refernce FP instructions. * Include GCC fix for Linaro bugzilla #2562: ARM GCC 5.2 call weak function instead of strong when called through pointer https://bugs.linaro.org/show_bug.cgi?id=2562 * Include GCC fix for Linaro bugzilla #1925: [regression] FAIL: libgomp.fortran/retval1.f90 -O1 execution test https://bugs.linaro.org/show_bug.cgi?id=1925 * Include GCC fix for Linaro bugzilla #2185: aarch64-linux-gnu-g++ internal compiler error: in curr_insn_transform https://bugs.linaro.org/show_bug.cgi?id=2185 * Backported glibc patch to simplify static malloc interposition [BZ #20432] to correct user identified issue. commit 058b5a41d56b9a8860dede14d97dd443792d064b Author: Florian Weimer Date: Fri Aug 26 22:40:27 2016 +0200 malloc: Simplify static malloc interposition [BZ #20432] * Host binaries for x86_64 linux hosts now have symbols and debug information stripped in order to reduce the size of the toolchain binary archives. This reduces the archive size from 1.1G to 580M for aarch64-linux-gnu target with the gcc-5-branch. * Removed .la files from binary toolchain archive as these files break autotools builds. https://bugs.linaro.org/show_bug.cgi?id=2764 * The mingw toolchains are now archived using the rsync -L option in order to avoid problems with Windows extractors and symbolic links. https://review.linaro.org/#/c/16415/ This resolves the following user bugs: https://bugs.linaro.org/show_bug.cgi?id=2684 https://bugs.linaro.org/show_bug.cgi?id=2192 https://bugs.linaro.org/show_bug.cgi?id=2762 * Copy the libwinpthread DLL into the bin directories so it gets into the tmp directory before tar is run. https://review.linaro.org/#/c/13723/ * Increment binutils release date to 2016_02 to reflect the most recent commit: commit ef90a4718f535cbe6345b4e7168baea7b1972abf Author: Matthew Wahab <matthew.wahab(a)arm.com> Date: Tue Jan 12 16:35:30 2016 +0000 [ARM] Support ARMv8.2 RAS extension. * Baremetal sysroot names now contain 'newlib' rather than 'glibc'. * Manifests now contain relative paths rather than absolute paths. * Now generating proper manifest files. * Fixed pi requeue support in glibc 2.21 while allowing the existing 2.21 minimum kernel default setting. This was checked into the linaro/2.21/master branch. commit a68cafa11c500d8a49a3014c43c5152859d037ae Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> Date: Tue May 17 10:16:39 2016 -0300 Add runtime check for __ASSUME_REQUEUE_PI (BZ# 18463) commit 6e5cb616b5b442ce8b2664ad673c0acf42a490ac Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> Date: Mon May 16 19:01:10 2016 -0300 Remove __ASSUME_SET_ROBUST_LIST commit 9ac61c0047295696cbcdbc26bdc174c7bd25a3c8 Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> Date: Mon May 16 10:35:25 2016 -0300 Remove __ASSUME_FUTEX_LOCK_PI * Backported support into GCC for Cortex-A32, Cortex-A35, and Cortex-R8. * Applied fix for CVE-2015-7547 - 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, Linaro GCC 5.3-2016.02, Linaro GCC 5.3-2016.03, Linaro GCC 5.3-2016.04, Linaro GCC 5.4-2016.06, Linaro GCC 5.4-2016.10, Linaro GCC 5.4-2016.12, Linaro GCC 5.4-2017.02, GCC 5.4-2017.04 and Linaro GCC 5.5-2017.10 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/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.02 http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.03 http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.04 http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.4-2016.06 http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.4-2016.10 http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.4-2016.12 http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.4-2017.02 http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.4-2017.04 http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.5-2017.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

8 years

Does Linaro GCC 5.4 fully support ARMv8.2-A

by Vincent Chen

Hi, We are evaluating LInaro GCC5.4 readiness for ARMv8.2-A extension support but can't find direct answer if all the features has been supported/backported. Can you point me to the answer? Thanks, Vincent ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -----------------------------------------------------------------------------------

8 years

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain