linaro-toolchain

linaro-toolchain@lists.linaro.org

16 participants
5599 discussions

Re: [Linaro-TCWG-CI] gcc patch #109141: Failure on aarch64

by Christophe Lyon

Hi, We had a "disk full" issue on that machine, sorry for the false alarm. We can manually retrigger the build if you wish? Thanks, Christophe On Tue, 25 Mar 2025 at 12: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. > > In gcc_build master-aarch64, after: > | gcc patch https://patchwork.sourceware.org/patch/109141 > | Author: Tobias Burnus <tburnus(a)baylibre.com> > | Date: Tue Mar 25 10:32:08 2025 +0100 > | > | [Patch] omp-general.cc: Remove 'if' around call to always 'true' returning function [PR118627] > | > | I intent to commit this a bit later today as obvious, > | unless there are comments. > | > | ... 35 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 7679b826840 opcodes: fix wrong code in expand_binop_directly [PR117811] > > Produces Failure: > | Results changed to > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe gcc: > | # FAILED > | > | From > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe gcc: > | 1 > > Used configuration : > *CI config* tcwg_gcc_build master-aarch64 > *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu > > If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways to reproduce a debug environment: > > You can find the failure logs in > * https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/17126/ar… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/17126/ar… > > Current build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/17126/ar… > Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/3294/artifac… > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files.

3 months

Re: [Linaro-TCWG-CI] gcc patch #109137: Failure on aarch64

by Christophe Lyon

Hi, We had a "disk full" issue on that machine, sorry for the false alarm. We can manually retrigger the build if you wish? Thanks, Christophe On Tue, 25 Mar 2025 at 12:22, <ci_notify(a)linaro.org> wrote: > > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In gcc_build master-aarch64, after: > | gcc patch https://patchwork.sourceware.org/patch/109137 > | Author: Sam James <sam(a)gentoo.org> > | Date: Tue Mar 25 07:54:09 2025 +0000 > | > | [PATCH] testsuite: add testcase for recent alias fix > | > | r15-7961-gdc47161c1f32c3 fixes a typo in ao_compare::compare_ao_refs > | but there wasn't a testcase available at the time. Now there is. > | > | ... 8 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 7679b826840 opcodes: fix wrong code in expand_binop_directly [PR117811] > > Produces Failure: > | Results changed to > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe gcc: > | # FAILED > | > | From > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe gcc: > | 1 > > Used configuration : > *CI config* tcwg_gcc_build master-aarch64 > *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu > > If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways to reproduce a debug environment: > > You can find the failure logs in > * https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/17124/ar… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/17124/ar… > > Current build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/17124/ar… > Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/3294/artifac… > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files.

3 months

Request to update Clang in libc++ pre-commit CI

by Mark de Wever

Hi, Clang 20 has been released and per libc++ policy we want to remove support for Clang 18. While testing a patch to remove Clang 18 support [1] I noticed the ARM buildbots you maintain failed [2] since they use Clang 18. Would it be possible to update these bots to Clang 20 or Clang 19? [1] https://github.com/llvm/llvm-project/pull/130142 [2] https://buildkite.com/llvm-project/libcxx-ci/builds/41081 Kind regards, Mark

3 months

https://github.com/llvm/llvm-project/pull/131921

by Louis Dionne

Hi, We have encountered a CI failure on a libc++ CI bot owned by this list. I am seeking assistance to help debug the issue since it's a bit difficult to do without having access to that platform. This is time sensitive for us, since the patch fixes a real issue we encountered and we'd like to get it fixed in the LLVM 20 release. See https://github.com/llvm/llvm-project/pull/131921#issuecomment-2737539434 for more details. Thanks, Louis

3 months

Re: [Linaro-TCWG-CI] gcc-15-8649-g1d2257dc850: 1 regressions on arm

by Richard Earnshaw (lists)

On 21/03/2025 20:36, ci_notify(a)linaro.org wrote: > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In gcc_check master-arm, after: > | commit gcc-15-8649-g1d2257dc850 > | Author: Richard Earnshaw <rearnsha(a)arm.com> > | Date: Fri Mar 21 15:20:03 2025 +0000 > | > | arm: testsuite: make unaligned-memcpy-*.c executable tests [PR91614] > | > | These tests have been looking for a very specific instruction sequence > | which has the tendency to be fairly unstable as a result. But what is > | more interesting is that the the tests must not contain instructions > | ... 22 lines of the commit log omitted. > > Produces 1 regressions: > | > | regressions.sum: > | Running gcc:gcc.target/arm/arm.exp ... > | FAIL: gcc.target/arm/unaligned-memcpy-4.c scan-assembler-not unaligned Should be fixed now. The scanner was matching 'unaligned' in a .file directive containing the test name. R. > > Used configuration : > *CI config* tcwg_gcc_check master-arm > *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1545. Please let us know if you have a fix. > > If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways to reproduce a debug environment: > > You can find the failure logs in *.log.1.xz files in > * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3580/artifact/ar… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3580/artifact/ar… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3580/artifact/ar… > > Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3580/artifact/ar… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3579/artifact/ar… > > Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > > Full commit : https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=1d2257dc850d088f6d9267b46…

3 months

[Linaro-TCWG-CI] gcc-15-8650-g94fa9f4d27b: 6 regressions on arm

by Paul Richard Thomas

Hello there, You had previously warned me of the problem with the pre-commit patch, from which I was able to identify the problem. Unfortunately, I screwed up by only correcting the cast of 'dim' in three out of four places. Hans-Peter Nilsson has put it right and I believe that the regression will disappear. Thanks for your help on this. Paul

3 months

Re: [Linaro-TCWG-CI] gcc-15-8035-g7ee31bc9276: 2 regressions on master-thumb_m23_soft_eabi

by Jonathan Wakely

On Sun, 16 Mar 2025 at 13:16, <ci_notify(a)linaro.org> wrote: > > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In arm-eabi cortex-m23 soft, after: > | commit gcc-15-8035-g7ee31bc9276 > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Thu Mar 13 13:34:55 2025 +0000 > | > | libstdc++: Implement <stdbit.h> for C++26 (P3370R1) > | > | This is the first part of the P3370R1 proposal just approved by the > | committee in Wrocław. This adds C++ equivalents of the functions added > | to C23 by WG14 N3022. > | ... 16 lines of the commit log omitted. > > Produces 2 regressions: > | > | regressions.sum: > | Running libstdc++:libstdc++-dg/conformance.exp ... > | FAIL: 20_util/stdbit/1.cc -std=gnu++26 (test for excess errors) > | UNRESOLVED: 20_util/stdbit/1.cc -std=gnu++26 compilation failed to produce executable > > Used configuration : > *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv8-m.base -mtune=cortex-m23 -mfloat-abi=soft -mfpu=auto > *configure and test flags:* --target arm-eabi --disable-multilib --with-mode=thumb --with-cpu=cortex-m23 --with-float=soft --target_board=-mthumb/-march=armv8-m.base/-mtune=cortex-m23/-mfloat-abi=soft/-mfpu=auto qemu_cpu=cortex-m33 > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1543. Please let us know if you have a fix. All the errors are of the form: error: 'ULLONG_MAX' was not declared in this scope but the test includes <limits.h>. So this target doesn't support long long? Or just doesn't define ULLONG_MAX?

3 months, 1 week

Re: [Linaro-TCWG-CI] llvmorg-21-init-4020-gf01e760c0836: 6235 regressions on aarch64

by Ricardo Jesus

Hi, Sorry for this issue, I've reverted this in: https://github.com/llvm/llvm-project/commit/21610e3ecc8bc727f99047e544186b3… Before I start digging into it further, could you please let me know what hardware is used to run these tests? I just thought I'd double-check that the requested -msve-vector-bits=256 does match the hardware SVE length. Thanks very much, Ricardo On 3/7/25 09:03, ci_notify(a)linaro.org wrote: > [You don't often get email from ci_notify(a)linaro.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] > > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In tcwg_flang_test/main-aarch64-Ofast-sve_vls-lto-lld, after: > | commit llvmorg-21-init-4020-gf01e760c0836 > | Author: Ricardo Jesus <rjj(a)nvidia.com> > | Date: Thu Mar 6 09:27:07 2025 +0000 > | > | [AArch64][SVE] Improve fixed-length addressing modes. (#129732) > | > | When compiling VLS SVE, the compiler often replaces VL-based offsets > | with immediate-based ones. This leads to a mismatch in the allowed > | addressing modes due to SVE loads/stores generally expecting immediate > | ... 29 lines of the commit log omitted. > > Produces 6235 regressions: > | > | regressions.sum: > | Running test-suite:Fujitsu/C/0000 ... > | FAIL: test-suite :: Fujitsu/C/0000/Fujitsu-C-0000_0003.test > | FAIL: test-suite :: Fujitsu/C/0000/Fujitsu-C-0000_0004.test > | FAIL: test-suite :: Fujitsu/C/0000/Fujitsu-C-0000_0008.test > | FAIL: test-suite :: Fujitsu/C/0000/Fujitsu-C-0000_0009.test > | ... and 6513 more > | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one > > Used configuration : > * Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;openmp;clang-tools-extra" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld > * Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH} > cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" > > We track this bug report under https://linaro.atlassian.net/browse/LLVM-1592 Please let us know if you have a fix. > > If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways to reproduce a debug environment: > > You can find the failure logs in *.log.1.xz files in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…>> The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…>> The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…>> > Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/>> > Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…>> Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…>> > Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…>> > Full commit : https://github.com/llvm/llvm-project/commit/f01e760c08365426de95f02dc2c2dc6…>

3 months, 1 week

[Linaro-TCWG-CI] glibc-2.41.9000-173-g997f49fbadf: 1 regressions on aarch64

by ci_notify＠linaro.org

Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In glibc_check master-aarch64, after: | commit glibc-2.41.9000-173-g997f49fbadf | Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> | Date: Mon Mar 17 19:08:22 2025 +0000 | | elf: Fix tst-origin make rules | | Add tests-special before include Rules and compile liborigin.os with | MODULE_NAME set to testsuite instead of libc. Produces 1 regressions: | | regressions.sum: | Running glibc:. ... | FAIL: lint-makefiles Used configuration : *CI config* tcwg_glibc_check master-aarch64 *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu We track this bug report under https://linaro.atlassian.net/browse/GNU-1544. Please let us know if you have a fix. If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. -----------------8<--------------------------8<--------------------------8<-------------------------- The information below contains the details of the failures, and the ways to reproduce a debug environment: You can find the failure logs in *.log.1.xz files in * https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2594/artif… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2594/artif… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2594/artif… Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2594/artif… Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2592/artif… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=997f49fbadf892136c77…

3 months, 1 week

[Linaro-TCWG-CI] glibc-2.41.9000-168-g9b646f5dc93: 3 regressions on arm

by ci_notify＠linaro.org

Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In glibc_check master-arm, after: | commit glibc-2.41.9000-168-g9b646f5dc93 | Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> | Date: Tue Feb 18 15:58:16 2025 -0500 | | elf: Canonicalize $\ORIGIN in an explicit ld.so invocation [BZ 25263] | | When an executable is invoked directly, we calculate $\ORIGIN by calling | readlink on /proc/self/exe, which the Linux kernel resolves to the | target of any symlinks. However, if an executable is run through ld.so, | ... 24 lines of the commit log omitted. Produces 3 regressions: | | regressions.sum: | Running glibc:elf ... | UNRESOLVED: elf/tst-origin | Running glibc:malloc ... | FAIL: malloc/tst-mallocfork2 | FAIL: malloc/tst-mallocfork3 Used configuration : *CI config* tcwg_glibc_check master-arm *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf We track this bug report under https://linaro.atlassian.net/browse/GNU-1540. Please let us know if you have a fix. If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. -----------------8<--------------------------8<--------------------------8<-------------------------- The information below contains the details of the failures, and the ways to reproduce a debug environment: You can find the failure logs in *.log.1.xz files in * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2551/artifact/… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2551/artifact/… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2551/artifact/… Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2551/artifact/… Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2550/artifact/… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=9b646f5dc933dfa019f2…

3 months, 2 weeks

← Newer
1
2
3
4
5
6
7
8
9
...
560
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain