linaro-toolchain

linaro-toolchain@lists.linaro.org

10 participants
5485 discussions

[ACTIVITY] 6 - 10 January 2019

by Diana Picus

== Progress == * Out of office until Tuesday * LLVM 9.0.1 - Uploaded final binaries - Still looking into PR44157 (CFI tests failing on armv7) * Morello LLDB - Trying to get bare metal debugging to work * More ARM Code of Conduct courses etc == Plan == * More Morello and PR44157

4 years, 10 months

[ACTIVITY] 2-3 January 2020

by Christophe Lyon

Short "week" == Progress == * BFD Linker: - GNU-629: non-contiguous memory support: Cleaning up, adding testcases. * GCC upstream validation: - reported/checked a few issues * misc: - infra fixes / troubleshooting / reviews == Next == * Binutils: GNU-629: support non-contiguous memory regions in linker

4 years, 10 months

[ACTIVITY] week ending 22 Dec 2019

by Richard Henderson

* Patch set cleaning up PIE/non-PIE linking - Add new support for static pie. * Another revision removing MMU_MODE_SUFFIX. * Random patch review. * Planning for Linux on ARM summit in Cambridge in February. r~

4 years, 11 months

Bot failure caused by f72d001e099871fd5943679a8377f2fcc675f860

by Michael Trent

To whom, I’m seeing a failure on this bot: -- Command Output (stderr): -- /home/buildslave/buildslave/clang-cmake-armv7-quick/stage1/bin/llvm-objdump: error: '/home/buildslave/buildslave/clang-cmake-armv7-quick/llvm/llvm/test/tools/llvm-objdump/Inputs/macho-stabs-x86_64': can't find target: : error: unable to get target for 'x86_64---macho', see --version and --triple. This is just a binary file verifier. Is it the case this bot doesn’t have a mach-o disassembler? And if so, is there a way to disable this test on this bot? Thanks! MDT

4 years, 11 months

[ACTIVITY] week ending Dec. 22 2019

by Alex Bennée

QEMU Tooling ([VIRT-252]) ========================= Extend gdbstub for SVE ([VIRT-281]) - posted [PATCH v4 00/21] gdbstub refactor and SVE support (+check-tcg tweaks) Message-Id: <20191220120438.16114-1-alex.bennee(a)linaro.org> [VIRT-281] <https://projects.linaro.org/browse/VIRT-281> GSoC Mentoring Afermath ([VIRT-348]) - started working on re-base of [TCG code quality tracking] - bit of a re-factor rethink required [TCG code quality tracking] <https://github.com/stsquad/qemu/tree/tcg/tbstats-and-perf-v10> Upstream Work ([VIRT-109]) ========================== - posted [PULL 00/25] testing and logging updates Message-Id: <20191219104934.866-1-alex.bennee(a)linaro.org> - posted [PATCH v1 0/4] semihosting read console support Message-Id: <20191218180029.6744-1-alex.bennee(a)linaro.org> - posted [PATCH v2 0/5] semihosting read console support Message-Id: <20191220132246.6759-1-alex.bennee(a)linaro.org> [VIRT-109] <https://projects.linaro.org/browse/VIRT-109> Completed Reviews [4/4] ======================= {PATCH} Semihost SYS_READC implementation (v6) Message-Id: <20191104204230.12249-1-keithp(a)keithp.com> - CLOSING NOTE [2019-12-18 Wed 19:39] Found some issues with deadlocks, fixed and sent my own series including this patch. Added: <2019-12-06 Fri> [PATCH] docker: gtester is no longer used Message-Id: <1576632611-55032-1-git-send-email-pbonzini(a)redhat.com> - CLOSING NOTE [2019-12-20 Fri 12:20] Queued to my tree Added: <2019-12-18 Wed> {Qemu-devel} {RFC PATCH} Implement qemu_thread_yield for posix, use it in mttcg to handle EXCP_YIELD Message-Id: <20190717054655.14104-1-npiggin(a)gmail.com> - CLOSING NOTE [2019-12-20 Fri 13:11] Replied. [PATCH v2 00/28] cputlb: Remove support for MMU_MODE*_SUFFIX Message-Id: <20191216221158.29572-1-richard.henderson(a)linaro.org> Absences ======== - Christmas and New Year holidays Current Review Queue ==================== * [RFC PATCH 00/13] hw/timer/allwinner: Make it reusable Message-Id: <20191219185127.24388-1-f4bug(a)amsat.org> Added: <2019-12-19 Thu> * [PATCH v2 00/14] chardev: Use QEMUChrEvent enum in IOEventHandler typedef Message-Id: <20191218172009.8868-1-philmd(a)redhat.com> Added: <2019-12-18 Wed> * [RFC PATCH v3 000/132] Proof of concept for Meson integration Message-Id: <1576155176-2464-1-git-send-email-pbonzini(a)redhat.com> Added: <2019-12-12 Thu> * {PATCH 0/2} tests/acceptance: Add boot vmlinux test Message-Id: <20191206140012.15517-1-wainersm(a)redhat.com> Added: <2019-12-06 Fri> -- Alex Bennée

4 years, 11 months

[ACTIVITY] report week ending 20 Dec

by Peter Maydell

Progress (covers two weeks; lost half of last week to the cold that's been going around the office here): * VIRT-65 [QEMU upstream maintainership] - code review + RTH's ARMv8.2-UAO patchset + RTH's ARMv8.1-PAN patchset + had a look at Huawei SDEI patchset; there are some things I don't like about the approach but I don't currently have any better ideas :-( Sent an email to the list to see if others have any suggestions. + Andrew Jones' patchset to pause the virtual timer when VM is paused + Some smmuv3 emulation fixes from Amazon + Support for emulating generic timers that run at platform-dependent frequency (rather than insisting they always run at 62.5MHz) - release work + herded a handful of key bugfixes into rc5; got rc5 and then the final release out of the door + got new s390 box into the set of machines we test QEMU on (IBM want to turn off the old one at the end of the year) + a couple of arm pull requests now 5.0 is open for new contributions thanks -- PMM

4 years, 11 months

[ACTIVITY] 16 - 20 December 2019

by Diana Picus

== Progress == * LLVM 9.0.1 - Had trouble with our TK1 machine - Trying to build rc3 on one of the buildbots - AArch64 rc3 looks fine * Morello - Got lldb-server working on android and it seems to behave fine - Working on getting the lldb test-suite to work in remote mode with the morello android simulator - Running into all sorts of issues with it == Plan == * More of the same * Out of office: 25-26 December, 1-7 January

4 years, 11 months

PE/COFF arm64 bdf/binutils targets

by Dimitri John Ledkov

One cannot use objcopy --target=efi-app-aarch64 because it appears that PE/COFF targets are not enabled for aarch64. Making UEFI & Windows on Snapdragon work harder. Given that Windows 10 is fully supported on aarch64, I assume it does have PE/COFF. Can someone please fix bfd to provide PE targets on aarch64? -- Regards, Dimitri.

4 years, 11 months

[ACTIVITY] 16-20 Dec 2019

by Christophe Lyon

== Progress == * GCC: - -mpure-code on v6m: committed. - investigated potential problem with -mno-unaligned-access. It was a wrong-user-code case, but maybe it would be desirable to implement an option like llvm's -arm-assume-misaligned-load-store * BFD Linker: - GNU-629: non-contiguous memory support: Now able to detect cases where input sections change size during the linker iterations and when linker-created stubs would cause overflows. * GCC upstream validation: - reported/checked a few issues * misc: - infra fixes / troubleshooting / reviews == Next == * Binutils: GNU-629: support non-contiguous memory regions in linker * Holidays: Dec 23rd-Jan 2nd

4 years, 11 months

clang-cmake-armv7-selfhost build failure

by John McCall

There’s been an ongoing failure on the clang-cmake-armv8-selfhost builder for the last day or so; see e.g.: http://lab.llvm.org:8011/builders/clang-cmake-armv7-selfhost/builds/2827/ This list is recorded as the contact information for that builder. It is apparently crashing in a tblgen backend that I just added: ``` Stack dump: 0. Program arguments: /home/buildslave/buildslave/clang-cmake-armv7-selfhost/stage1/bin/clang-tblgen -gen-clang-type-writer -I /home/buildslave/buildslave/clang-cmake-armv7-selfhost/llvm/clang/include -I /home/buildslave/buildslave/clang-cmake-armv7-selfhost/llvm/clang/include/clang/AST -I /home/buildslave/buildslave/clang-cmake-armv7-selfhost/llvm/llvm/include /home/buildslave/buildslave/clang-cmake-armv7-selfhost/llvm/clang/include/clang/AST/TypeProperties.td --write-if-changed -o /home/buildslave/buildslave/clang-cmake-armv7-selfhost/stage1/tools/clang/include/clang/AST/AbstractTypeWriter.inc Segmentation fault (core dumped) ``` I would like to fix this, but I have no ability to reproduce it, and the crash information in the log is quite minimal. Is there a way I can get a shell on a system that can reproduce this, or at the very least get a line number for where exactly it is crashing? John.

4 years, 11 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain