linaro-toolchain

linaro-toolchain@lists.linaro.org

6 participants
5605 discussions

[ACTIVITY] 20-24 April 2020

by Christophe Lyon

== Progress == * GCC upstream validation: - reported a couple of failures/regressions * GCC: - Committed a few fixes to MVE/CDE tests to avoid failures on arm-linux-gnueabi toolchains - Sent a few more testcases fixes - PR94538 (pure-code/M23): Let Wilco handle it since he has more testcases - Looked at Linaro bug #5614, and forwarded it for upstream discussion as PR94743 (IRQ handler and Neon registers) * FDPIC/GDB: - rebased gdbserver patches, it still crashes at runtime. Code size bigger than my last attempt with gdb-8.x. - tried to link it statically, but that fails because of multiple defs in uclibc. * misc: - infra fixes / troubleshooting / reviews - lots of disruptions == Next == * FDPIC GDB * GCC/cortex-M

5 years, 2 months

Re: buildbot failure in LLVM on clang-cmake-armv8-lld

by David Blaikie

Looks like there might be something wrong with this buildbot? (none of the commits seem to have changed lnt - or maybe lnt isn't monitored/blamed in the buildbot config?) On Tue, Apr 21, 2020 at 12:16 AM <llvm.buildmaster(a)lab.llvm.org> wrote: > The Buildbot has detected a new failure on builder clang-cmake-armv8-lld > while building llvm. > Full details are available at: > http://lab.llvm.org:8011/builders/clang-cmake-armv8-lld/builds/3875 > > Buildbot URL: http://lab.llvm.org:8011/ > > Buildslave for this Build: linaro-armv8-01-arm-lld > > Build Reason: scheduler > Build Source Stamp: [branch master] > c2d86e1f3044abb295796c8267c7b9057f54a067 > Blamelist: Alexander Shaposhnikov <alexshap(a)fb.com>,Chris Bieneman < > chris.bieneman(a)me.com>,Dan Liew <dan(a)su-root.co.uk>,David Blaikie < > dblaikie(a)gmail.com>,Johannes Doerfert <johannes(a)jdoerfert.de>,Mircea > Trofin <mtrofin(a)google.com>,Pavel Iliin <Pavel.Iliin(a)arm.com>,Sam Kerner < > skerner(a)chromium.org>,Shengchen Kan <shengchen.kan(a)intel.com>,Sriraman > Tallam <tmsriram(a)google.com> > > BUILD FAILED: failed setup lit > > sincerely, > -The Buildbot > > > >

5 years, 2 months

[ACTIVITY] 2 weeks ending 19 Apr 2020

by Richard Henderson

Short weeks around Easter. [VIRT-349 # QEMU SVE2 Support ] Lots of progress on insn implementation. Several patches from Stephen Long merged. He's coming up to speed nicely. Some good review from Laurent Desnogues. Spent some time writing a version of strspn for Arm optimized-routines, as a way of testing the NMATCH instruction. Found bugs in the tcg optimizer instead. Still in the process of rebasing the branch upon those fixes, and upon patch review from Peter. [VIRT-327 # Richard's upstream QEMU work ] Couple of patches for 5.0. [GCC] Posted v4 of aarch64 cmpti patch set. r~

5 years, 2 months

[ACTIVITY] week ending Apr. 19 2020

by Alex Bennée

VirtIO Related Work ([VIRT-366]) ================================ [VIRT-366] <https://projects.linaro.org/browse/VIRT-366> VirtIO RPMB ([VIRT-371]) - started work on [vhost-user backend for rpmb] - have the basic vhost-user loop created, still need to plumb into QEMU - will be able to experiment with [VIRT-402] minimal profile once running [VIRT-371] <https://projects.linaro.org/browse/VIRT-371> [vhost-user backend for rpmb] <https://github.com/stsquad/qemu/tree/vhost-user-rpmb> [VIRT-402] <https://projects.linaro.org/browse/VIRT-402> VirtiIO blogpost ([LBO-2]) - wrote up history of VirtIO up to standardisation - still TODO new work and architectures [LBO-2] <https://projects.linaro.org/browse/LBO-2> slides with virtio architectures for Victor Upstream Work ([VIRT-109]) ========================== - posted [PULL for 5.0-rc3 0/8] a few small fixes (docker, user, pie and gdbstub) Message-Id: <20200415104211.9388-1-alex.bennee(a)linaro.org> [VIRT-109] <https://projects.linaro.org/browse/VIRT-109> Other ===== - preparation work and GSoC candidate interviews [my QEMU developer guide] <https://people.linaro.org/~alex.bennee/org/presentations/qemu-developer-gui…> Absences ======== - Home-schooling in mornings Current Review Queue ==================== * [RFC][PATCH v2 0/3] IVSHMEM version 2 device for QEMU Message-Id: <cover.1578407802.git.jan.kiszka(a)siemens.com> Added: <2020-04-09 Thu> * [PATCH v6 00/36] Initial support for multi-process qemu Message-Id: <cover.1586165555.git.elena.ufimtseva(a)oracle.com> Added: <2020-04-06 Mon> * [PATCH v4 00/10] tests/vm: Add support for aarch64 VMs Message-Id: <20200312142728.12285-1-robert.foley(a)linaro.org> Added: <2020-03-27 Fri> -- Alex Bennée

5 years, 2 months

[ACTIVITY] report week ending 17 Apr

by Peter Maydell

(short week, 3 days) Progress: * VIRT-65 [QEMU upstream maintainership] - getting rc3 out of the door, including sorting out some last minute bug fixes. As usual, we hope not to need an rc4 but I expect we will. - code review; a two-day blitz has got my to-review queue down to a slightly more manageable size... + rth's series refactoring SVE load/store implementation + Guenter's i.MX watchdog support series + brief pass over raspi USB host controller emulation series + patch adding /secure-chosen/kaslr-seed to the virt dtb + the Greensocs/Xilinx clock framework patchset [including doing an editing pass on the docs] thanks -- PMM

5 years, 2 months

How to use 'runtime-linaro-...' and 'sysroot-linaro-...' archives ?

by Константин Аладышев

Hello! I know, this is probably a very stupid question, but I couldn't find an answer for it. On the page https://releases.linaro.org/components/toolchain/binaries/latest-5/arm-linu… there are 3 major download components: gcc/sysroot/runtime. I download 'gcc', add 'gcc-linaro-.../bin' to my PATH and cross compile my apps. On my target system, I need 'libc', and it is present in the 'sysroot-linaro-...'. Do I need to copy all of the contents of 'sysroot-linaro-...' folder to my target? 'linaro-sysroot' folder is kinda big. 'libc.so' library is 13MB. If there is a way to decrease its size, if I want to use Linaro compiled programs on an embedded target? And what is a purpose of 'runtime-linaro-..." component?

5 years, 2 months

How to use 'runtime-linaro-...' and 'sysroot-linaro-...' archives ?

by Konstantin Aladyshev

5 years, 2 months

[ACTIVITY] 6 - 10 April 2020

by Prathamesh Kulkarni

== This Week == * LLVM-611 (tune heuristic to lower blx): Working on feedback. * GNU-659: Doing benchmarking experiments * Public holiday - One day off == Next Week == - Continue with LLVM-611 and GNU-659

5 years, 3 months

[ACTIVITY] 6-10 April 2020

by Christophe Lyon

== Progress == * GCC upstream validation: - reported a couple of failures/regressions * GCC: - comparing testsuite results for cortex-m3 and cortex-m33 with cortex-a9 to check what cortex-M problem there are. Updated cmse-15.c test. Analyzing / bisecting other failures. - Sent fixes to MVE tests to avoid failures on arm-linux-gnueabi toolchains - Updated a few bugzilla entries about cortex-m issues * misc: - infra fixes / troubleshooting / reviews == Next == * FDPIC GDB * GCC/cortex-M

5 years, 3 months

Disk full on linaro-tk1-06 (buildbot failure in LLVM on clang-cmake-armv7-full)

by Ilya Leoshkevich

Hi, clang-cmake-armv7-full fails with "No space left on device", e.g.: http://lab.llvm.org:8011/builders/clang-cmake-armv7-full/builds/9808/steps/… > The Buildbot has detected a new failure on builder clang-cmake-armv7- full while building llvm. > Full details are available at: > http://lab.llvm.org:8011/builders/clang-cmake-armv7-full/builds/9808 > > Buildbot URL: http://lab.llvm.org:8011/ > > Buildslave for this Build: linaro-tk1-06 > > Build Reason: scheduler > Build Source Stamp: [branch master] 3bc439bdff8bb5518098bd9ef52c56ac071276bc > Blamelist: Ilya Leoshkevich <iii(a)linux.ibm.com> > > BUILD FAILED: failed Checkout test-suite > > sincerely, > -The Buildbot Could someone please take a look? Best regards, Ilya

5 years, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain