linaro-toolchain

linaro-toolchain@lists.linaro.org

4 participants
5637 discussions

by Ryan Arnold

== Progress == * CbuildV2 Fixes to add fetch md5sums to testsuite/test.sh: - Subject: [PATCH][test_fetch_md5sums 1/2] lib/fetch.sh: Add missing ${local_snapshots} to md5sum path. - Subject: [PATCH][test_fetch_md5sums 2/2] testsuite/test.sh: Add fetch tests section. * CbuildV2 Fixes to get testsuite/test.sh working in the source directory: - Subject: [PATCH][cbuild2 1/3] testsuite/test.sh: Don't use "warning" function before it is sourced. - Subject: [PATCH][cbuild2 2/3] testsuite/test.sh: Remove redundant sourcing of host.conf. - Subject: [PATCH][cbuild2 3/3] testsuite/test.sh: Re-enable running tests from src dir. CbuildV2 random fixes: - Subject: [PATCH][cbuild2 2/4] cbuild2.sh: correct --disable "boostrap" - Subject: [PATCH][cbuild2 3/4] config/ffmpeg.conf: separate options * CbuildV2 fixes to remove ${dir}/md5sums usage (it is redunant with snapshots/md5sums). - Subject: [PATCH][cbuild2 1/4] Remove unneeded infrastructure/md5sums fragment - Subject: [PATCH][cbuild2 4/4] Remove ${dir} specific md5sums files. * Fixed error where gcc stage 2 configure returns early (erroneously) on success. - [PATCH] Only return early on error following configure * Fixed error in downloading branch named git repos in lib/checkout.sh. - [PATCH] Fix git clone to get repo without branch name as part of the url. == Issues == Contacted its@linaro requesting permission to be able to create personal branches in rsavoye’s cbuild2 git tree. They created a group for cbuildv2. Got work laptop installed (dualboot) with Fedora 19 and ran into some errors with secure boot. == Plan == * Spend some time looking at our options with regard to EGLIBC options groups when forced to move to glibc proper. *

12 years

[ACTIVITY] Week 41

by Will Newton

== Progress == * Backports and release for binutils 2013.10 (x4!) * Backports and release for eglibc 2013.10 * Submitted a couple more glibc memalign patches * Committed aarch64 gdb fix * Bits of malloc work in between == Issues == * None == Plan == * Try and get some uninterrupted time on malloc -- Will Newton Toolchain Working Group, Linaro

12 years

[ACTIVITY] Week 41

by Renato Golin

== Progress == * EEMBC - Updating Linaro image with Clang toolchain changes - Updating compare_all script to rank boards - Investigating differences in performance against GCC * ODroid XU - Setting up server image (Linaro 13.09 + odroid specific changes) - CPU scheduler is a mess, forcing "performance" governor at boot seems to work - No journal in root fs, remounts ro all the time (bad image?) - LLVM builds are slow (as fast as Chromebook), maybe it's the SDCard - Setting it as self-host buildbot in the lab, going well * Background - Massive patch review (Sub-Register Live Range Analysis for NEON/VFP et al) - LLVM Sync and EuroLLVM meetings == Plan == * Continue investigating performance problems in EEMBC * Check Odroid XU internal buildbot for stability

12 years

Error

by Rick

Hi Term, I have try to us "crosstool-ng-linaro-1.13.1-4.8 "to build myself cross tool chain, but some problem happened,just before I have used crosstool-ng offcial version, every thing is fine,I have got my toolchain, my operation system is Ubuntu 12.10, when I change to crosstool-ng-linaro, I am follow these steps. ct-ng list-samples, ct-ng linaro-arm-linux-gnueabihf ct-ng menuconfig I just change Local tarballs directory ,Prefix directory ,and change target os from prebuilt to linux, then,I build it,first time error happened at step "cc_core_pass_1 ",I google it and found out it is about multilib,I need to install gcc-multilib and g++-multilib, then,I continue,this time,error happened at step"cc_core_pass_2 ". related messages in build.log: [ALL ] Supported emulations: armelf_linux armelf armelfb armelfb_linux [ERROR] collect2: error: ld returned 1 exit status [ERROR] make[4]: *** [libgcc_s.so] Error 1 [ALL ] make[4]: Leaving directory `/work/software/cortexa9-linaro-build/.build/arm-linux-gnueabihf/build/build-cc-core-shared/arm-linux-gnueabihf/arm-linux-gnueabi/libgcc' [ERROR] make[3]: *** [multi-do] Error 1 [ALL ] make[3]: Leaving directory `/work/software/cortexa9-linaro-build/.build/arm-linux-gnueabihf/build/build-cc-core-shared/arm-linux-gnueabihf/libgcc' [ERROR] make[2]: *** [all-multi] Error 2 [ALL ] make[2]: Leaving directory `/work/software/cortexa9-linaro-build/.build/arm-linux-gnueabihf/build/build-cc-core-shared/arm-linux-gnueabihf/libgcc' [ERROR] make[1]: *** [all-target-libgcc] Error 2 [ALL ] make[1]: Leaving directory `/work/software/cortexa9-linaro-build/.build/arm-linux-gnueabihf/build/build-cc-core-shared' [ERROR] [ERROR] >> [ERROR] >> Error happened in: main[scripts/crosstool-NG.sh] so,I really don't know how to do now,any help is welcome.Thank you Cheers,Rick

12 years

Does Linaro aarch64 gcc toolchain support Cortex-A53/A57 performance tunning.

by Zenon Xiu

Hi team, In the GCC.pdf of gcc-linaro-aarch64-none-elf-4.8-2013.08, it says that -mcpu supports cortex-a53, but when I tried to build a simple hello bare metal application with -mcpu=cortex-a53 option, gcc reports, Error: unknown cpu `cortex-a53' Error: unrecognized option -mcpu=cortex-a53 Could you please confirm whether Cortex-A53/A57 performance tunning is supported? Thanks. Best Regards. ------------------------------------------------------------------ Zenon Xiu -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590 ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782

12 years

[ANNOUNCE] Aarch64 toolchain binaries respin 2013.09-01 released

by Bernhard Rosenkränzer

We have spotted a problem with the GOT layout in binaries generated by the 2013.09 Aarch64 toolchain, causing them to crash on startup. New builds fixing this issue are now available at http://releases.linaro.org/13.09/components/toolchain/binaries The arm-linux-gnueabihf and arm-none-eabi toolchains are not affected by this problem - there is no respin version for those builds. 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: http://releases.linaro.org/13.09/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.

12 years

[ACTIVITY] Week 40

by Will Newton

== Progress == * Committed glibc ARM pointer encryption support. * Committed binutils AArch64 ifunc support. * Committed glibc malloc test patches. * Committed glibc setjmp/longjmp Thumb patches. * Backported glibc aarch64 gprof support. * Submitted qemu AArch32 VSEL patch. * Backported binutils AArch64 GOT layout patches. == Issues == * None == Plan == * Backports for 2013.10 * Follow up qemu patch * malloc -- Will Newton Toolchain Working Group, Linaro

12 years

[ACTIVITY] 29 Sept-4 Oct 2013

by Christophe Lyon

== Progress == * AArch64 frame grows downward: no feedback yet. * Disable-peeling: Vectorizer cost model has been changed upstream, the current default now includes the effect of disabling peeling. I have submitted benchmark jobs to check the exact effet; expecting some regressions since the reduced test case I was working on now generates the same code as with my patch. * AArch64 bootstrap failure: build it still on-going, so still hoping to reproduce it. * GCC trunk validation: - good progress on reporting - cross-validating several configurations (currently 18) for each upstream commit is too much for our compute farm to handle. Reduced to patches related to ARM/AArch64, but then we can miss regressions caused by other generic patches. * Backports: - committed a few simple ones. == Next == * AArch64 frame grows downward: continue * Disable-peeling/new vectorizer cost model: analyze bench results * Backports : check which ones can be reasonably done

12 years

[ACTIVITY] Week 40

by Yvan Roux

== Issues == * None. == Progress == * 2013-10 release. - Reviewed some backports. * LRA on AArch32: - Testsuite analysis showed one remaining issue in ARM mode (with the movmisalignv8hi_neon_store insn handling). - Ran Benchmarks on Calxedas, some failures due to the same bug. - Benchmarks on tcpandas ongoing. - Benchmarks results analysis ongoing. == Next == * Continue on LRA.

12 years

[ACTIVITY] 28 September -1 October 2013

by Venkataramanan Kumar

== Progress == * libssp Updated review comments given by glibc maintainer and rerun tests. There are some test failures, suspecting issue in using ALIGN_UP/DOWN macro. Debugging them. * gprof support for aarch64 Upstreamed patches to GCC and backported to Linaro 4.8 branch. Closed the cards for gprof work. * 1-1 Meet with Christophe. == Plan == * Continue libssp support. * Restart Aarch64 boot strap in a server machine. * Book hotel ticket for connect. * PGO for aarch64

12 years

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain