linaro-toolchain

linaro-toolchain@lists.linaro.org

9 participants
5482 discussions

Re: [Linaro-TCWG-CI] gcc-14-9268-g574fd1f17f1: FAIL: 15 regressions: 15 progressions on aarch64

by Christophe Lyon

Hi Patrick, This report can be considered as a false alarm: the errors were already present in the baseline, but the ICE line number changed since your patch modified the code in the file where the ICE occurs. That being said, I've noticed another report saying that your patch broke bootstrap on i686. Thanks, Christophe On Sat, 2 Mar 2024 at 20:38, <ci_notify(a)linaro.org> wrote: > > Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > We track this report status in https://linaro.atlassian.net/browse/GNU-1168 , please let us know if you are looking at the problem and/or when you have a fix. > > In master-aarch64 after: > > | commit gcc-14-9268-g574fd1f17f1 > | Author: Patrick Palka <ppalka(a)redhat.com> > | Date: Fri Mar 1 17:24:15 2024 -0500 > | > | c++/modules: depending local enums [PR104919, PR106009] > | > | For local enums defined in a non-template function or a function template > | instantiation it seems we neglect to make the function depend on the enum > | definition (which modules considers logically separate), which ultimately > | causes the enum definition to not be properly streamed before uses > | within the function definition are streamed. > | ... 75 lines of the commit log omitted. > > FAIL: 15 regressions: 15 progressions > > regressions.sum: > === g++ tests === > > Running g++:g++.dg/modules/modules.exp ... > FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6113) > FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++2a (internal compiler error: in core_vals, at cp/module.cc:6113) > FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6113) > FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6113) > FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++2a (internal compiler error: in core_vals, at cp/module.cc:6113) > FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6113) > FAIL: g++.dg/modules/xtreme-header-5_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6113) > ... and 9 more entries > > progressions.sum: > === g++ tests === > > Running g++:g++.dg/modules/modules.exp ... > FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++2a (internal compiler error: in core_vals, at cp/module.cc:6114) > FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6114) > FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6114) > FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6114) > FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++2a (internal compiler error: in core_vals, at cp/module.cc:6114) > FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6114) > FAIL: g++.dg/modules/xtreme-header-5_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6114) > ... and 9 more entries > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/9… > The full lists of regressions and progressions as well as configure and make commands are in > - https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/9… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/9… > > The configuration of this build is: > CI config tcwg_gnu_native_check_gcc master-aarch64 > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/9… > Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/9… > > Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > > Full commit : https://github.com/gcc-mirror/gcc/commit/574fd1f17f100c7c355ad26bc525ab5a33… > > List of configurations that regressed due to this commit : > * tcwg_gnu_native_check_gcc > ** master-aarch64 > *** FAIL: 15 regressions: 15 progressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/9…

8 months, 3 weeks

[ACTIVITY] report week ending 1 Mar

by Peter Maydell

Progress: * UM-2 [QEMU upstream maintainership] - code review, notably another round of the raspberry pi 4b emulation series. Reviewed and took a subset of the patches, which is enough to get a working model without PCI or ethernet. We'll work on the landing other parts, but no need to block the initial model on them. * QEMU-530 [QEMU ARMv9.5 Baseline CPU for TCG] - Started implementation of FEAT_ECV (enhanced counter virtualization); I have a preliminary set of patches which I am currently testing and hope to be able to send out early next week -- PMM

8 months, 3 weeks

Re: [Linaro-TCWG-CI] llvmorg-19-init-3481-g8c2ae42b3e1c: Failure on aarch64

by Nathan Chancellor

On Wed, Feb 28, 2024 at 02:47:11PM +0000, ci_notify(a)linaro.org wrote: > Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > We track this report status in https://linaro.atlassian.net/browse/LLVM-1153 , please let us know if you are looking at the problem and/or when you have a fix. > > In CI config tcwg_kernel/llvm-master-aarch64-lts-allyesconfig after: > > | commit llvmorg-19-init-3481-g8c2ae42b3e1c > | Author: Kupa-Martin <84517188+Kupa-Martin(a)users.noreply.github.com> > | Date: Tue Feb 27 11:58:59 2024 -0300 > | > | [Clang][Sema] Fix missing warning when comparing mismatched enums in … (#81418) > | > | …C mode > | > | Factored logic from `CheckImplicitConversion` into new methods > | `Expr::getEnumConstantDecl` and `Expr::getEnumCoercedType` for use in > | `checkEnumArithmeticConversions`. > | ... 2 lines of the commit log omitted. > > Results changed to > # reset_artifacts: > -10 > # build_abe binutils: > -9 > # build_kernel_llvm: > -5 > # build_abe qemu: > -2 > # linux_n_obj: > 37 > > From > # reset_artifacts: > -10 > # build_abe binutils: > -9 > # build_kernel_llvm: > -5 > # build_abe qemu: > -2 > # linux_n_obj: > 22291 > > The configuration of this build is: > CI config tcwg_kernel/llvm-master-aarch64-lts-allyesconfig > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-lts-allyesconfig… > Reference build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-lts-allyesconfig… > > Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > > Full commit : https://github.com/llvm/llvm-project/commit/8c2ae42b3e1c6aa7c18f873edcebff7… > > List of configurations that regressed due to this commit : > * tcwg_kernel > ** llvm-master-aarch64-lts-allyesconfig > *** Failure > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > *** https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-lts-allyesconfig… Thanks a lot for the report, this is expected with that change. How we want to handle this in the kernel is currently under discussion at https://github.com/ClangBuiltLinux/linux/issues/2002. Cheers, Nathan

8 months, 4 weeks

Re: [Linaro-TCWG-CI] 6 patches in binutils: FAIL: 1 regressions on aarch64

by Jan Beulich

On 23.02.2024 15:24, ci_notify(a)linaro.org wrote: > Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. So: The specific failure observed makes me guess that in the course of building generated files (opcodes/aarch64-*-2.c) aren't re-generated. If this is indeed the case, sending out such unsolicited emails (I've had a 2nd one in the meantime, for whatever reason) is a waste of everybody's time, even more so when not clearly indicating that fact, such that - quoting above - it is possible "within minutes" to understand what's going on / wrong. IOW - unless clarified I'm going to assume that the report here is a false negative. Jan > In binutils_check master-aarch64 after: > > | 6 patches in binutils > | Patchwork URL: https://patchwork.sourceware.org/patch/86276 > | 2d039d3b147 gas/NEWS: drop mention of Arm64's SVE2.1 and SME2.1 > | 38eca7294bd Arm64: correct SVE2.1 ld2q (scalar plus scalar) > | cb804986590 Arm64: correct SVE2.1 ld{3,4}q / st{3,4}q (scalar plus immediate) > | edaf01ca3b4 Arm64: check tied operand specifier in aarch64-gen > | 006ce007bc8 Arm64: check matching operands for predicated B16B16 insns > | ... and 1 more patches in binutils > | ... applied on top of baseline commit: > | e346d50a891 x86: rename vec_encoding and vex_encoding_* > > FAIL: 1 regressions > > regressions.sum: > === gas tests === > > Running gas:gas/aarch64/aarch64.exp ... > FAIL: Test of SVE2.1 instructions > > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/109… > The full lists of regressions and progressions as well as configure and make commands are in > - https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/109… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/109… > > The configuration of this build is: > CI config tcwg_binutils_check master-aarch64 > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/109… > Reference build : https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-build/797/art…

9 months

[ACTIVITY] report week ending 23 Feb

by Peter Maydell

Progress: * UM-2 [QEMU upstream maintainership] - code review - finished and sent out for review the patchset that provides a 3-phase-reset version of qemu_register_reset() - The MSYS2 project are dropping their support for 32-bit Windows, which affects QEMU because we use them for our "test build on Windows" CI jobs. This prompted us to drop our 32-bit Windows host support (which conveniently we'd already deprecated last year). Sent out patches to drop the CI jobs, document that it's not a supported platform, etc. thanks -- PMM

9 months

llvm lldb-aarch64-windows builder failing

by Ted Woodward

I apologize if this is the wrong email for this report. I got it from the "Worker" tab on a build on https://lab.llvm.org/buildbot/#/builders/219 . The build is failing at the build step. It's trying to run: ninja ^"^" ^"^" which is erroring out with ninja: error: empty path https://lab.llvm.org/buildbot/#/builders/219/builds/9644/steps/4/logs/stdio Ted

9 months

Re: [Linaro-TCWG-CI] gdb patch #85948: FAIL: 7 regressions: 1 progressions on arm

by Tiezhu Yang

On 02/21/2024 03:52 AM, ci_notify(a)linaro.org wrote: > If you can't get what you need from our CI within minutes, let us know and we will be happy to help. We can see "Operation not permitted" in the log info, please try one of the following processes to test: (1) set ptrace_scope as 0 $ echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope $ make check-gdb TESTS="gdb.threads/attach-many-short-lived-threads.exp" (2) use sudo $ sudo make check-gdb TESTS="gdb.threads/attach-many-short-lived-threads.exp" Thanks, Tiezhu

9 months

Re: [Linaro-TCWG-CI] gcc-14-9028-g7f3d900684a: FAIL: 1 regressions: 1 progressions on aarch64

by Jonathan Wakely

On Fri, 16 Feb 2024 at 19:03, <ci_notify(a)linaro.org> wrote: > > Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > We track this report status in https://linaro.atlassian.net/browse/GNU-1155 , please let us know if you are looking at the problem and/or when you have a fix. Reported as https://gcc.gnu.org/PR113961 and fixed. > In gcc_check master-aarch64 after: > > | commit gcc-14-9028-g7f3d900684a > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Wed Feb 7 11:31:10 2024 +0000 > | > | libstdc++: Fix FAIL: 26_numerics/random/pr60037-neg.cc [PR113931] > | > | PR libstdc++/87744 > | PR libstdc++/113931 > | > | libstdc++-v3/ChangeLog: > | > | ... 2 lines of the commit log omitted. > > FAIL: 1 regressions: 1 progressions > > regressions.sum: > === libstdc++ tests === > > Running libstdc++:libstdc++-dg/conformance.exp ... > FAIL: 26_numerics/random/pr60037-neg.cc -std=gnu++17 (test for errors, line 3350) > > > progressions.sum: > === libstdc++ tests === > > Running libstdc++:libstdc++-dg/conformance.exp ... > FAIL: 26_numerics/random/pr60037-neg.cc -std=gnu++17 (test for errors, line 271) > > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1615/artifac… > The full lists of regressions and progressions as well as configure and make commands are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1615/artifac… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1615/artifac… > > The configuration of this build is: > CI config tcwg_gcc_check master-aarch64 > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1615/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1614/artifac… > > Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > > Full commit : https://github.com/gcc-mirror/gcc/commit/7f3d900684ad989164114f25eb46a33871… > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-aarch64 > *** FAIL: 1 regressions: 1 progressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1615/artifac…

9 months, 1 week

Re: [Linaro-TCWG-CI] gcc-14-8998-gc9ce332b557: FAIL: 2 regressions on aarch64

by Jonathan Wakely

On Thu, 15 Feb 2024 at 21:31, <ci_notify(a)linaro.org> wrote: > > Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > We track this report status in https://linaro.atlassian.net/browse/GNU-1154 , please let us know if you are looking at the problem and/or when you have a fix. Also reported as https://gcc.gnu.org/PR113931 and now fixed. > > In gcc_check master-aarch64 after: > > | commit gcc-14-8998-gc9ce332b557 > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Wed Feb 7 11:31:10 2024 +0000 > | > | libstdc++: Use 128-bit arithmetic for std::linear_congruential_engine [PR87744] > | > | For 32-bit targets without __int128 we need to implement the LCG > | transition function by hand using 64-bit types. > | > | We can also slightly simplify the __mod function by using if-constexpr > | unconditionally, disabling -Wc++17-extensions warnings with diagnostic > | ... 13 lines of the commit log omitted. > > FAIL: 2 regressions > > regressions.sum: > === libstdc++ tests === > > Running libstdc++:libstdc++-dg/conformance.exp ... > FAIL: 26_numerics/random/pr60037-neg.cc -std=gnu++17 (test for errors, line 271) > FAIL: 26_numerics/random/pr60037-neg.cc -std=gnu++17 (test for excess errors) > > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1609/artifac… > The full lists of regressions and progressions as well as configure and make commands are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1609/artifac… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1609/artifac… > > The configuration of this build is: > CI config tcwg_gcc_check master-aarch64 > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1609/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1608/artifac… > > Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > > Full commit : https://github.com/gcc-mirror/gcc/commit/c9ce332b557bb95987d038d98ea929cdfd… > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-aarch64 > *** FAIL: 2 regressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1609/artifac…

9 months, 1 week

Fwd: [Linaro-TCWG-CI] glibc patch #85585: FAIL: 1 regressions on arm

by H.J. Lu

FAIL: elf/tst-gnu2-tls2 indicates that your _dl_tlsdesc_dynamic may not preserve all caller-saved registers. Please find out how the test fails. H.J. ---------- Forwarded message --------- From: <ci_notify(a)linaro.org> Date: Wed, Feb 14, 2024 at 3:50 PM Subject: [Linaro-TCWG-CI] glibc patch #85585: FAIL: 1 regressions on arm To: <hjl.tools(a)gmail.com> Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. In glibc_check master-arm after: | glibc patch https://patchwork.sourceware.org/patch/85585 | Author: H.J. Lu <hjl.tools(a)gmail.com> | Date: Sun Feb 11 19:19:49 2024 -0800 | | x86-64: Update _dl_tlsdesc_dynamic to preserve vector registers | | Compiler generates the following instruction sequence for GNU2 dynamic | TLS access: | | leaq tls_var@TLSDESC(%rip), %rax | call *tls_var@TLSCALL(%rax) | ... 13 lines of the commit log omitted. | ... applied on top of baseline commit: | dbae3a3940 trivial doc fix: remove weird phrase "syscall takes zero to five arguments" FAIL: 1 regressions regressions.sum: === glibc tests === Running glibc:elf ... FAIL: elf/tst-gnu2-tls2 You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/1460/artif… The full lists of regressions and progressions as well as configure and make commands are in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/1460/artif… The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/1460/artif… The configuration of this build is: CI config tcwg_glibc_check master-arm -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/1460/artif… Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/953/artifact/a… -- H.J.

9 months, 1 week

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain