- linaro-toolchain - lists.linaro.org

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

by Jerry D

This is part of a large patch set and can not be tested individually by the bots. Cheers, Jerry On 2/24/26 5:06 PM, 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/130593 > | Author: Andre Vehreschild <vehre(a)gcc.gnu.org> > | Date: Thu Feb 12 11:17:47 2026 -0800 > | > | [PATCH] Fortran: Add a shared memory coarray implementation [PR88076] > | > | Add caf_shmem, a shared memory multi process coarray implementation. > | The library adheres to the existing coarray ABI and is controlled by > | environment variables for selecting the number of images and virtual > | ... 15 lines of the commit log omitted. > | ... applied on top of baseline commit: > | ad590516056 RISC-V: Change scratch constraint for _lra insns. > > Produces Failure: > | Results changed to > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe gcc: > | # FAILED > | # First few build errors in logs: > | # 00:18:48 make[2]: *** [Makefile:1866: all] Error 2 > | # 00:18:48 make[1]: *** [Makefile:15837: all-target-libgfortran] Error 2 > | # 00:18:48 make: *** [Makefile:1099: all] Error 2 > | > | 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/20609/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/20609/ar… > > Current build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/20609/ar… > Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/4425/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.

1 month, 4 weeks

1
0
0 0

[Linaro-TCWG-CI] v6.19-rc1-6-g9b8a0ba68246a: Failure 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 master-arm, after: | commit v6.19-rc1-6-g9b8a0ba68246a | Author: Christian Brauner <brauner(a)kernel.org> | Date: Mon Dec 29 14:03:24 2025 +0100 | | mount: add OPEN_TREE_NAMESPACE | | When creating containers the setup usually involves using CLONE_NEWNS | via clone3() or unshare(). This copies the caller's complete mount | namespace. The runtime will also assemble a new rootfs and then use | ... 54 lines of the commit log omitted. Produces Failure: | Results changed to | # reset_artifacts: | -10 | # true: | 0 | # build_abe binutils: | 1 | # build_abe stage1 --: | 2 | # build_abe linux: | 3 | # build_abe glibc: | # FAILED | # build_abe stage2 --: | # build_abe gdb: | # build_abe qemu: | # First few build errors in logs: | # 00:05:26 ../sysdeps/unix/sysv/linux/sys/mount.h:267:9: error: ‘OPEN_TREE_CLONE’ redefined [-Werror] | # 00:05:26 make[2]: *** [/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-linux-gnueabihf/glibc-glibc.git~master/sysd-rules:111: /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-linux-gnueabihf/glibc-glibc.git~master/misc/umount.o] Error 1 | # 00:05:26 make[1]: *** [Makefile:484: misc/subdir_lib] Error 2 | # 00:05:26 make: *** [Makefile:20: all] Error 2 | | From | # reset_artifacts: | -10 | # true: | 0 | # build_abe binutils: | 1 | # build_abe stage1 --: | 2 | # build_abe linux: | 3 | # build_abe glibc: | 4 | # build_abe stage2 --: | 5 | # build_abe gdb: | 6 | # build_abe qemu: | 7 Used configuration : *CI config* tcwg_gnu_cross_build master-arm *configure and test flags:* --target arm-linux-gnueabihf We track this bug report under https://linaro.atlassian.net/browse/GNU-1845. 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 * https://ci.linaro.org/job/tcwg_gnu_cross_build--master-arm-build/1380/artif… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_gnu_cross_build--master-arm-build/1380/artif… Current build : https://ci.linaro.org/job/tcwg_gnu_cross_build--master-arm-build/1380/artif… Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_build--master-arm-build/1379/artif… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/linux… Full commit : https://gitlab.com/Linaro/lkft/mirrors/torvalds/linux-mainline/commit/9b8a0…

2 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-16-7593-g39edc2aea24f: 4 regressions on aarch64

by Jonathan Wakely

On Thu, 19 Feb 2026 at 23:09, <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-aarch64, after: > | commit gcc-16-7593-g39edc2aea24f > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Tue Feb 17 12:48:51 2026 +0000 > | > | libstdc++: Use global variables for default/max std in libstdc++.exp > | > | This simplifies the v3-minimum-std procedure slightly, but the main > | advantage is making v3_modules_std depend on v3_max_std so that we don't > | have to update two separate variables when new effective targets such as > | ... 12 lines of the commit log omitted. > > Produces 4 regressions: > | > | regressions.sum: > | Running libstdc++:libstdc++-dg/conformance.exp ... > | ERROR: tcl error code TCL WRONGARGS > | ERROR: tcl error sourcing libstdc++-dg/conformance.exp. > | UNRESOLVED: testcase libstdc++-dg/conformance.exp' aborted due to Tcl error > | ERROR: wrong # args: should be "v3-minimum-std test default_std max_std" > > Used configuration : > *CI config* tcwg_gcc_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-1842. Please let us know if you have a fix. This should be fixed at r16-7599-g8d8725bedd2f7c > > 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-aarch64-build/4763/artifac… > 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-aarch64-build/4763/artifac… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/4763/artifac… > > Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/4763/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/4762/artifac… > > Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s… > > Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git

2 months

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-23-init-2712-g7ccdc06780b0: 2 regressions on aarch64

by Parzyszek, Krzysztof

[AMD Official Use Only - AMD Internal Distribution Only] This should be fixed by https://github.com/llvm/llvm-project/pull/180583. Commit: https://github.com/llvm/llvm-project/commit/0e7ddf395a12e0201ed0ca7131439c2… -Krzysztof ________________________________ From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> Sent: Wednesday, February 11, 2026 7:39 AM To: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com> Cc: Parzyszek, Krzysztof <Krzysztof.Parzyszek(a)amd.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org> Subject: [Linaro-TCWG-CI] llvmorg-23-init-2712-g7ccdc06780b0: 2 regressions on aarch64 Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding. 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-23-init-2712-g7ccdc06780b0 | Author: Krzysztof Parzyszek <Krzysztof.Parzyszek(a)amd.com> | Date: Wed Feb 4 07:20:20 2026 -0600 | | [flang][OpenMP] Leave local automatic variables alone (#178739) | | There is code in resolve-directives.cpp that tries to apply DSA flags to | symbols encountered inside constructs. This code was written with the | assumption that all such symbols will be declared outside of the | ... 14 lines of the commit log omitted. Produces 2 regressions: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/0160 ... | FAIL: test-suite :: Fujitsu/Fortran/0160/Fujitsu-Fortran-0160_0012.test | FAIL: test-suite :: Fujitsu/Fortran/0160/Fujitsu-Fortran-0160_0013.test | # "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;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -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/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/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 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite" We track this bug report under https://linaro.atlassian.net/browse/LLVM-2175. 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://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/… Full commit : https://github.com/llvm/llvm-project/commit/7ccdc06780b05bd8f31c20a9734fca2…

2 months, 1 week

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-16-7292-g3f790555048: 2 regressions on aarch64

by Nathan Myers

Fixed as of 9b85fcc00ebe850f2ee2c19a0208534544b088a8 On 2/6/26 1:32 PM, 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 master-aarch64, after: > | commit gcc-16-7292-g3f790555048 > | Author: Nathan Myers <ncm(a)cantrip.org> > | Date: Mon Sep 22 23:52:52 2025 -0400 > | > | libstdc++: container erasure overloads (P2077) [PR117404] > | > | Remaining to do: > | * Add new declarations in debug headers too. > | > | ... 48 lines of the commit log omitted. > > Produces 2 regressions: > | > | regressions.sum: > | Running g++:g++.dg/dg.exp ... > | FAIL: g++.dg/concepts/expression.C -std=gnu++17 (test for excess errors) > | UNRESOLVED: g++.dg/concepts/expression.C -std=gnu++17 compilation failed to produce executable > > Used configuration : > *CI config* tcwg_gnu_cross_check_gcc master-aarch64 > *configure and test flags:* --target aarch64-linux-gnu > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1831. 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_gnu_cross_check_gcc--master-aarch64-build/25… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/25… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/25… > > Current build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/25… > Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/25… > > Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s… > > Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git

2 months, 2 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-16-5627-g4e7213aa081f: 1 regression on master-thumb_m55_hard_eabi

by Tomasz Kaminski

Hi, I am unable to reproduce the issue, and cannot access the included log files to check the failure. Could you please share the revelant part of log, at least from time/hash.cc? On Fri, Jan 9, 2026 at 10:23 PM <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-m55 hard, after: > | commit gcc-16-5627-g4e7213aa081f > | Author: Tomasz Kamiński <tkaminsk(a)redhat.com> > | Date: Wed Nov 26 14:28:39 2025 +0100 > | > | libstdc++: Fix typo in operator used in __pack_ints [PR122864] > | > | `<=` was used instead of `<<`, this was detected by clang warning. > | > | PR libstdc++/122864 > | ... 5 lines of the commit log omitted. > > Produces 1 regression: > | > | regressions.sum: > | Running libstdc++:libstdc++-dg/conformance.exp ... > | FAIL: std/time/hash.cc -std=gnu++26 execution test > > Used configuration : > *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb > -march=armv8.1-m.main+mve.fp+fp.dp -mtune=cortex-m55 -mfloat-abi=hard > -mfpu=auto > *configure and test flags:* --target arm-eabi --disable-multilib > --with-mode=thumb --with-arch=armv8.1-m.main+mve.fp+fp.dp --with-float=hard > --target_board=-mthumb/-march=armv8.1-m.main+mve.fp+fp.dp/-mtune=cortex-m55/-mfloat-abi=hard/-mfpu=auto > qemu-cpu=cortex-m55 > > We track this bug report under > https://linaro.atlassian.net/browse/GNU-1806. 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_gnu_embed_check_gcc--master-thumb_m55_hard_e… > The full lists of regressions and improvements as well as configure and > make commands are in > * > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m55_hard_e… > The list of [ignored] baseline and flaky failures are in > * > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m55_hard_e… > > Current build : > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m55_hard_e… > Reference build : > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m55_hard_e… > > Instruction to reproduce the build : > https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s… > > Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git

2 months, 2 weeks

2
1
0 0

Re: [Linaro-TCWG-CI] gcc-16-7209-gc035985fd611: 4 regressions 4 fixes on arm

by Alexandre Oliva

On Jan 31, 2026, ci_notify(a)linaro.org wrote: > | regressions.sum: > | Running gcc:gcc.target/arm/arm.exp ... > | FAIL: gcc.target/arm/crypto-vsha1cq_u32.c scan-assembler-times > | vdup.32\\tq[0-9]+, (?:r[0-9]+|d[0-9]+\\[[0-9]+\\]) 4 > | > | fixes.sum: > | Running gcc:gcc.target/arm/arm.exp ... > | FAIL: gcc.target/arm/crypto-vsha1cq_u32.c scan-assembler-times > | vdup.32\\tq[0-9]+, r[0-9]+ 4 That looks like still the same failure, but since the pattern is textually different, it is no longer recognized as the same test point. Unfortunately, the code this test run of yours generates doesn't match the new pattern either. I guess the pattern will need to be extended further. -- Alexandre Oliva, happy hacker https://blog.lx.oliva.nom.br/ Free Software Activist FSFLA co-founder GNU Toolchain Engineer More tolerance and less prejudice are key for inclusion and diversity. Excluding neuro-others for not behaving ""normal"" is *not* inclusive!

2 months, 3 weeks

1
0
0 0

RE: [Linaro-TCWG-CI] gcc-16-6913-g304d08fea9e6: 1 regression on arm

by Prathamesh Kulkarni

Hi, Thanks for the report. I have posted patch to fix the issue: https://gcc.gnu.org/pipermail/gcc-patches/2026-January/707277.html Can you please check if the above patch fixes the issue at your end ? Thanks, Prathamesh > -----Original Message----- > From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> > Sent: 23 January 2026 13:39 > To: Prathamesh Kulkarni <prathameshk(a)nvidia.com> > Cc: gcc-regression(a)gcc.gnu.org; mmalcolmson(a)nvidia.com > Subject: [Linaro-TCWG-CI] gcc-16-6913-g304d08fea9e6: 1 regression on > arm > > External email: Use caution opening links or attachments > > > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). > Please find some details below. > > In master-arm, after: > | commit gcc-16-6913-g304d08fea9e6 > | Author: Matthew Malcolmson <mmalcolmson(a)nvidia.com> > | Date: Tue Jan 20 03:54:51 2026 +0000 > | > | libgomp: Ensure memory sync after performing tasks > | > | As described in PR 122356 there is a theoretical bug around > not > | "publishing" user data written in a task when that task has > been > | executed by a thread after entry to a barrier. > | ... 89 lines of the commit log omitted. > > Produces 1 regression: > | > | regressions.sum: > | Running libgomp:libgomp.c/c.exp ... > | FAIL: libgomp.c/pr122356.c execution test > > Used configuration : > *CI config* tcwg_gnu_cross_check_gcc master-arm *configure and test > flags:* --target arm-linux-gnueabihf > > We track this bug report under > https://linaro.atlassian.net/browse/GNU-1822. 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_gnu_cross_check_gcc--master-arm- > build/2581/artifact/artifacts/00-sumfiles/ > The full lists of regressions and improvements as well as configure > and make commands are in > * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm- > build/2581/artifact/artifacts/notify/ > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm- > build/2581/artifact/artifacts/sumfiles/xfails.xfail > > Current build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc-- > master-arm-build/2581/artifact/artifacts > Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc-- > master-arm-build/2580/artifact/artifacts > > Instruction to reproduce the build : > https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/- > /raw/master/gcc/sha1/304d08fea9e68c5b4806532816b58d33a15a917d/tcwg_gnu > _cross_check_gcc/master-arm/reproduction_instructions.txt > > Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git

2 months, 3 weeks

1
0
0 0

[Linaro-TCWG-CI] binutils-2_41-release-9539-g737979d0b3d: 2 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 master-aarch64, after: | commit binutils-2_41-release-9539-g737979d0b3d | Author: Richard Ball <richard.ball(a)arm.com> | Date: Tue Jan 28 17:06:58 2025 +0000 | | gas: implement parsing of object attributes v2 | | This patch adds the parsing logic for Object Attributes v2 (OAv2), enabling | Gas to interpret and process these attributes correctly. It also updates the | AArch64 backend to utilize the new parsing capabilities, and handle the new | ... 65 lines of the commit log omitted. Produces 2 regressions: | | regressions.sum: | Running gcc:gcc.target/aarch64/aarch64.exp ... | FAIL: gcc.target/aarch64/bti-1.c scan-assembler .section\t.note.gnu.property | FAIL: gcc.target/aarch64/bti-1.c scan-assembler .word\t0x7\t// GNU_PROPERTY_AARCH64_FEATURE_1_AND \$BTI, PAC, GCS\$ Used configuration : *CI config* tcwg_gnu_cross_check_gcc master-aarch64 *configure and test flags:* --target aarch64-linux-gnu We track this bug report under https://linaro.atlassian.net/browse/GNU-1828. 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_gnu_cross_check_gcc--master-aarch64-build/25… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/25… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/25… Current build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/25… Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/25… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/binut… Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=737979d0b3d3c…

2 months, 3 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-16-5975-gfae0c626250: 1 regression on master-thumb_m23_soft_eabi

by Andrew Pinski

On Wed, Jan 21, 2026 at 5:50 AM <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-16-5975-gfae0c626250 > | Author: Andrew Pinski <andrew.pinski(a)oss.qualcomm.com> > | Date: Sat Dec 6 01:11:29 2025 -0800 > | > | final_cleanup: Call make_forwarders_with_degenerate_phis [PR46555] > | > | This fixes a regression introduced with r16-5258-g1d8e2d51e5c5cb. > | With GCC 12+, we would not merge forwarders (with phis, vops included), > | this meant that after the last cddce, degenerate phis would stay not > | ... 22 lines of the commit log omitted. > > Produces 1 regression: > | > | regressions.sum: > | Running gcc:gcc.dg/tree-ssa/tree-ssa.exp ... > | FAIL: gcc.dg/tree-ssa/pr46555.c scan-rtl-dump pro_and_epilogue "Performing shrink-wrapping" > > 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-1819. Please let us know if you have a fix. Filed https://gcc.gnu.org/bugzilla/show_bug.cgi?id=123751 and fixed in r16-6969-g41878c161c480. Thanks, Andrew > > 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_gnu_embed_check_gcc--master-thumb_m23_soft_e… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m23_soft_e… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m23_soft_e… > > Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m23_soft_e… > Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m23_soft_e… > > Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s… > > Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git

3 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-16-6301-gb3c167b61fd7: 4 regressions on arm

by Tomasz Kaminski

Hi, This should be resolved by following commit that I have just pushed: commit 5513935f48e50e97c854b746e758842c846a7740 Author: Tomasz Kamiński <tkaminsk(a)redhat.com> Date: Wed Jan 7 17:24:55 2026 +0100 libstdc++: Use tree-dump-gimple in variant constant init tests. Use of scan-assembler-dem for matching against debug symbols, turned out to not be portable, as they representation in assembly output differs between platforms: arm use 60 columns limit, emitting multiple rows, and some platforms may encode them using base64. We use tree-dump-gimple instead, that outputs a constructor name portably, allowing us to simply match for invocation of constructor for given type, as each variable has different type. To use scan-tree-dump(-not) we load scantree.exp file and it's dependency scandump.exp from gcc/testsuite/lib. libstdc++-v3/ChangeLog: * testsuite/20_util/variant/constinit.cc: Use scan-tree-dump for matching of constructor. * testsuite/20_util/variant/constinit_compat.cc: Likewise. * testsuite/lib/libstdc++.exp: Load scantree.exp and scandump.exp. Regards, Tomasz On Thu, Dec 25, 2025 at 8:42 AM <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 master-arm, after: > | commit gcc-16-6301-gb3c167b61fd7 > | Author: Tomasz Kamiński <tkaminsk(a)redhat.com> > | Date: Thu Dec 11 10:43:44 2025 +0100 > | > | libstdc++: Use union to store non-trivially destructible types in > C++17 mode [PR112591] > | > | This patch disables use of specialization _Uninitialized<_Type, > false> for > | non-trivially destructible types by default in C++17, and > fallbacks to > | the primary template, that stores the type in union directly. > This makes the > | ... 39 lines of the commit log omitted. > > Produces 4 regressions: > | > | regressions.sum: > | Running libstdc++:libstdc++-dg/conformance.exp ... > | FAIL: 20_util/variant/constinit.cc -std=gnu++20 scan-assembler-dem > (std::in_place_index_t<1ul?>, double&&) > | FAIL: 20_util/variant/constinit.cc -std=gnu++20 scan-assembler-dem > (std::in_place_index_t<1ul?>, int&&) > | FAIL: 20_util/variant/constinit_compat.cc -std=gnu++20 > scan-assembler-dem (std::in_place_index_t<1ul?>, double&&) > | FAIL: 20_util/variant/constinit_compat.cc -std=gnu++20 > scan-assembler-dem (std::in_place_index_t<1ul?>, int&&) > > Used configuration : > *CI config* tcwg_gnu_cross_check_gcc master-arm > *configure and test flags:* --target arm-linux-gnueabihf > > We track this bug report under > https://linaro.atlassian.net/browse/GNU-1793. 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_gnu_cross_check_gcc--master-arm-build/2498/a… > The full lists of regressions and improvements as well as configure and > make commands are in > * > https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/2498/a… > The list of [ignored] baseline and flaky failures are in > * > https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/2498/a… > > Current build : > https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/2498/a… > Reference build : > https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/2497/a… > > Instruction to reproduce the build : > https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s… > > Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git

3 months, 2 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-16-5947-ga6c50ec2c6e: 6 regressions on arm

by H.J. Lu

On Tue, Dec 30, 2025 at 11:36 PM <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 v7-a softfp, after: > | commit gcc-16-5947-ga6c50ec2c6e > | Author: H.J. Lu <hjl.tools(a)gmail.com> > | Date: Fri Oct 24 09:00:59 2025 +0800 > | > | Add -ffuse-ops-with-volatile-access > | > | Volatile memory can be used as source operand for any operations. Add > | -ffuse-ops-with-volatile-access to fuse operations with volatile memory > | reference and update simplify_binary_operation_1 to keep PLUS for 2 > | ... 227 lines of the commit log omitted. > > Produces 6 regressions: > | > | regressions.sum: > | Running gcc:gcc.target/arm/arm.exp ... > | FAIL: gcc.target/arm/bfloat16_scalar_1_2.c check-function-bodies stacktest1 > | FAIL: gcc.target/arm/bfloat16_scalar_2_2.c check-function-bodies stacktest1 > | FAIL: gcc.target/arm/bfloat16_scalar_3_2.c check-function-bodies stacktest1 > | FAIL: gcc.target/arm/bfloat16_simd_1_2.c check-function-bodies stacktest1 Please check if the outputs are functional correct. > | ... and 2 more > > Used configuration : > *CI config* tcwg_gnu_embed_check_gcc arm-eabi -marm -march=armv7-a -mfpu=vfpv3-d16 -mfloat-abi=softfp > *configure and test flags:* --target arm-eabi --disable-multilib --with-mode=arm --with-arch=armv7-a --with-fpu=vfpv3-d16 --with-float=softfp --target_board=-marm/-march=armv7-a/-mfpu=vfpv3-d16/-mfloat-abi=softfp qemu_cpu=cortex-a9 > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1798. 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_gnu_embed_check_gcc--master-arm_v7a_softfp_e… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e… > > Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e… > Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e… > > Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s… > > Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git -- H.J.

3 months, 3 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-16-6185-g487bd3ba4f1f: Failure on arm

by Jonathan Wakely

On Fri, 19 Dec 2025 at 16:40, <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 bootstrap_build master-arm-bootstrap_O3, after: > | commit gcc-16-6185-g487bd3ba4f1f > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Wed Dec 10 14:26:17 2025 +0000 > | > | libstdc++: Optimize compilation time for signed/unsigned integer traits > | > | Replace the O(n) definitions using __is_one_of with constant-time > | checks that look for a static member in the __is_integral_helper class > | template. That class template is already specialized for every signed > | ... 20 lines of the commit log omitted. > > Produces Failure: > | Results changed to > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe bootstrap_O3: > | # FAILED > | # First few build errors in logs: > | # 00:49:05 /home/tcwg-buildslave/workspace/tcwg_gnu_3/abe/builds/armv8l-unknown-linux-gnueabihf/armv8l-unknown-linux-gnueabihf/gcc-gcc.git~master-stage2/prev-armv8l-unknown-linux-gnueabihf/libstdc++-v3/include/bits/stl_bvector.h:183:9: internal compiler error: Segmentation fault > | # 00:49:05 make[3]: *** [Makefile:1216: text-art/ruler.o] Error 1 > | # 00:49:05 make[2]: *** [Makefile:5200: all-stage3-gcc] Error 2 > | # 00:49:05 make[1]: *** [Makefile:26599: stage3-bubble] Error 2 > | # 00:49:05 make: *** [Makefile:1127: all] Error 2 > | > | From > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe bootstrap_O3: > | 1 > > Used configuration : > *CI config* tcwg_bootstrap_build master-arm-bootstrap_O3 > *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1783. 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. Very strange - I don't know why this would trigger a segfault in the compiler. > > -----------------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_bootstrap_build--master-arm-bootstrap_O3-bui… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_bootstrap_build--master-arm-bootstrap_O3-bui… > > Current build : https://ci.linaro.org/job/tcwg_bootstrap_build--master-arm-bootstrap_O3-bui… > Reference build : https://ci.linaro.org/job/tcwg_bootstrap_build--master-arm-bootstrap_O3-bui… > > Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s… > > Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git

4 months

1
0
0 0

Re: [Linaro-TCWG-CI] v6.18-rc6-688-gcd41d3420ef6: Failure on arm

by Nathan Chancellor

On Mon, Dec 08, 2025 at 03:55:08AM +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. > > In tcwg_kernel/llvm-master-arm-mainline-allyesconfig, after: > | commit v6.18-rc6-688-gcd41d3420ef6 > | Author: Jaroslav Kysela <perex(a)perex.cz> > | Date: Wed Nov 26 10:16:35 2025 +0100 > | > | ASoC: nau8325: add missing build config > | > | This configuration was missing from the initial commit. > | > | Found by Jiri Benc <jbenc(a)redhat.com> > | ... 6 lines of the commit log omitted. > > Produces Failure: > | Results changed to > | # reset_artifacts: > | -10 > | # build_abe binutils: > | -9 > | # build_kernel_llvm: > | -5 > | # build_abe qemu: > | -2 > | # linux_n_obj: > | 23374 > | # First few build errors in logs: > | # 00:26:11 sound/soc/codecs/nau8325.c:430:13: error: variable 'n2_max' is uninitialized when used here [-Werror,-Wuninitialized] > | # 00:26:11 sound/soc/codecs/nau8325.c:431:11: error: variable 'ratio_sel' is uninitialized when used here [-Werror,-Wuninitialized] Should be hidden with https://git.kernel.org/broonie/c/2c7e5e17c05f1d5e10e63e1baff2b362cd08dcd6 but I am still not convinced that is a correct fix (but I don't really care to push further on it). https://lore.kernel.org/20251203214958.GC3060476@ax162/ Cheers, Nathan

4 months, 2 weeks

1
0
0 0

[PATCH RFA] libstdc++: add more #if to std.cc (was Re: [Linaro-TCWG-CI] gcc-16-5581-g3ad2e2d707c3: 1 regression on arm)

by Jason Merrill

On 12/6/25 11:52 AM, 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 v7-a softfp, after: > | commit gcc-16-5581-g3ad2e2d707c3 > | Author: Jason Merrill <jason(a)redhat.com> > | Date: Tue Nov 11 15:58:01 2025 +0530 > | > | driver/c++: add --compile-std-module > | > | For simple testcases that want to use the std module, it would be useful to > | have a reasonably short way to request building the binary module form > | before the testcase. So with this patch users can write > | ... 31 lines of the commit log omitted. > > Produces 1 regression: > | > | regressions.sum: > | Running g++:g++.dg/modules/modules.exp ... > | FAIL: g++.dg/modules/compile-std1.C -std=c++26 (test for excess errors) It seems that module std doesn't compile on arm-eabi, which is good to know. There seem to be two general issues: first, that some of the <stdio.h> functions that <print> relies on aren't declared: > /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-sta\ > ge2/arm-eabi/libstdc++-v3/include/print: In member function 'virtual void std::__format::_File_sink::_M_o\ > verflow()': > /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-sta\ > ge2/arm-eabi/libstdc++-v3/include/print:197:20: error: '::fwrite_unlocked' has not been declared; did you\ > mean '_fwrite_unlocked_r'? > /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-sta\ > ge2/arm-eabi/libstdc++-v3/include/print: In constructor 'std::__format::_File_sink::_File_sink(FILE*, boo\ > l)': > /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-sta\ > ge2/arm-eabi/libstdc++-v3/include/print:212:9: error: '::flockfile' has not been declared; did you mean '\ > _flockfile'? > /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-sta\ > ge2/arm-eabi/libstdc++-v3/include/print: In destructor 'std::__format::_File_sink::~_File_sink()': > /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-sta\ > ge2/arm-eabi/libstdc++-v3/include/print:218:11: error: '::putc_unlocked' has not been declared; did you m\ > ean '_putc_unlocked_r'? > /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-sta\ > ge2/arm-eabi/libstdc++-v3/include/print:219:9: error: '::funlockfile' has not been declared; did you mean\ > '_funlockfile'? It seems that newlib doesn't declare these functions under -std=c++26, only -std=gnu++26. I don't know what the right approach to this is. and then a bunch of "not declared" exports, such as > /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-sta\ > ge2/arm-eabi/libstdc++-v3/include/bits/std.cc:1002:14: error: 'condition_variable' has not been declared \ > in 'std' This looks like just needing to add more #if to std.cc, as below. OK for trunk? Incidentally, is it expected that arm-eabi doesn't support gthread? Jason

4 months, 2 weeks

2
1
0 0

[Linaro-TCWG-CI] binutils-2_41-release-8935-ga5818f278a3: 6 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 binutils_check master-aarch64, after: | commit binutils-2_41-release-8935-ga5818f278a3 | Author: Nick Clifton <nickc(a)redhat.com> | Date: Thu Dec 4 11:29:47 2025 +0000 | | Add warning message to readelf for local symbols that reference beyond the end of a mergeable section. Produces 6 regressions: | | regressions.sum: | Running ld:ld-elf/shared.exp ... | FAIL: Build rdynamic-1 | Running ld:ld-ifunc/ifunc.exp ... | FAIL: Checking ifunc binaries | FAIL: test-1 contains IFUNC symbols | ... and 5 more Used configuration : *CI config* tcwg_binutils_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-1772. 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_binutils_check--master-aarch64-build/2987/ar… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-build/2987/ar… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-build/2987/ar… Current build : https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-build/2987/ar… Reference build : https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-build/2986/ar… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/binut… Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=a5818f278a356…

4 months, 2 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] gdb-17-branchpoint-981-gcc1fc6af415: 77 regressions on arm

by Jan Vraný

Hi, unfortunately I do not have arm system at hand. I tried to build this commit on QEMU (qemu-system-arm) running Debian (armhf architecture) and I cannot reproduce any of the regressions. I'd appreciate some information on how to build and run suitable armv8l system on QEMU (or, if that's easier, on Odroid-N2) - I could not find much. Thanks! Jan On Sun, 2025-11-30 at 10:46 +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. > > In gdb_check master-arm, after: > | commit gdb-17-branchpoint-981-gcc1fc6af415 > | Author: Jan Vrany <jan.vrany(a)labware.com> > | Date: Fri Nov 28 13:47:02 2025 +0000 > | > | gdb: change blockvector::contains() to handle blockvectors with "holes" > | > | This commit slightly changes the logic in blockvector::contains() > | to handle a case where the blockvector contains blocks with disjoint > | regions (see the comment in blockvector::contains for details). > | ... 18 lines of the commit log omitted. > > Produces 77 regressions: > | > | regressions.sum: > | Running gdb:gdb.base/annota1.exp ... > | FAIL: gdb.base/annota1.exp: send SIGUSR1 (timeout) > | Running gdb:gdb.base/annota3.exp ... > | FAIL: gdb.base/annota3.exp: send SIGUSR1 (pattern 8) > | Running gdb:gdb.base/sigstep.exp ... > | ... and 87 more > > Used configuration : > *CI config* tcwg_gdb_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-1767. 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_gdb_check--master-arm-build/3149/artifact/ar… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/3149/artifact/ar… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/3149/artifact/ar… > > Current build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/3149/artifact/ar… > Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/3148/artifact/ar… > > Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gdb/s… > > Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=cc1fc6af4150b…

4 months, 2 weeks

3
7
0 0

[Linaro-TCWG-CI] binutils-2_41-release-8827-gbeab972c07d: 1 regression 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 binutils_check master-aarch64, after: | commit binutils-2_41-release-8827-gbeab972c07d | Author: H.J. Lu <hjl.tools(a)gmail.com> | Date: Sat Nov 15 11:43:45 2025 +0800 | | elf: Verify base symbol version works properly | | Add a testcase to verify that VER_NDX_GLOBAL can be used with | | asm (".symver foo_base, foo@"); | ... 15 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running ld:ld-elfvers/vers.exp ... | FAIL: Run pr33577a with tmpdir/libpr33577-versioned.so Used configuration : *CI config* tcwg_binutils_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-1759. 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_binutils_check--master-aarch64-build/2975/ar… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-build/2975/ar… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-build/2975/ar… Current build : https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-build/2975/ar… Reference build : https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-build/2974/ar… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/binut… Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=beab972c07d53…

4 months, 4 weeks

3
7
0 0

Re: [Linaro-TCWG-CI] llvmorg-22-init-14324-g02c68b3ef754: 1 regression 3 fixes on aarch64

by Luke Lau

Hi there, thanks for picking up on this change. I see there’s 1 regression and 3 fixes, I just want to check are the fixes previous miscompiles? Thanks, Luke > On 17 Nov 2025, at 09: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. > > In tcwg_flang_test/main-aarch64-Ofast-sve_vls-lto-lld, after: > | commit llvmorg-22-init-14324-g02c68b3ef754 > | Author: Luke Lau <luke(a)igalia.com> > | Date: Wed Nov 12 19:14:53 2025 +0800 > | > | [VPlan] Plumb scalable register size through narrowInterleaveGroups (#167505) > | > | On RISC-V narrowInterleaveGroups doesn't kick in because the wrong > | VectorRegWidth is passed to isConsecutiveInterleaveGroup. > | > | ... 10 lines of the commit log omitted. > > Produces 1 regression 3 fixes: > | > | regressions.sum: > | Running test-suite:Fujitsu/Fortran/0363 ... > | FAIL: test-suite :: Fujitsu/Fortran/0363/Fujitsu-Fortran-0363_0283.test > | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one > | > | fixes.sum: > | Running test-suite:Fujitsu/Fortran/0105 ... > | FAIL: test-suite :: Fujitsu/Fortran/0105/Fujitsu-Fortran-0105_0091.test > | ... and 2 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;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -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/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/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 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite" > > We track this bug report under https://linaro.atlassian.net/browse/LLVM-2121. 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://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/… > > Full commit : https://github.com/llvm/llvm-project/commit/02c68b3ef7544b875da4052dfb58205…

4 months, 4 weeks

2
1
0 0

[Linaro-TCWG-CI] glibc-2.42.9000-537-gcd748a63ab1: 5 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 master-aarch64, after: | commit glibc-2.42.9000-537-gcd748a63ab1 | Author: Joseph Myers <josmyers(a)redhat.com> | Date: Thu Nov 20 19:30:27 2025 +0000 | | Implement C23 const-preserving standard library macros | | C23 makes various standard library functions, that return a pointer | into an input array, into macros that return a pointer to const when | the relevant argument passed to the macro is a pointer to const. (The | ... 35 lines of the commit log omitted. Produces 5 regressions: | | regressions.sum: | Running gcc:gcc.dg/analyzer/analyzer.exp ... | FAIL: gcc.dg/analyzer/strchr-1.c (test for warnings, line 32) | FAIL: gcc.dg/analyzer/strchr-1.c (test for warnings, line 39) | FAIL: gcc.dg/analyzer/strchr-1.c (test for excess errors) | FAIL: gcc.dg/analyzer/strchr-1.c event at line 33 (test for warnings, line 32) | ... and 1 more Used configuration : *CI config* tcwg_gnu_native_check_gcc 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-1756. 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_gnu_native_check_gcc--master-aarch64-build/2… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/2… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/2… Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/2… Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/2… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/glibc… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=cd748a63ab1a7ae84617…

5 months

4
4
0 0

[Linaro-TCWG-CI] glibc-2.42.9000-514-g8d999a69936: 2 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 master-arm, after: | commit glibc-2.42.9000-514-g8d999a69936 | Author: H. Peter Anvin <hpa(a)zytor.com> | Date: Mon Oct 20 13:42:09 2025 -0700 | | linux/termios: clear k_termios.c_cflag & CIBAUD for non-split speed [BZ 33340] | | After getting more experience with the various broken direct-to-ioctl | termios2 hacks using Fedora 43 beta, I have found a fair number of | cases where the software would fail to set, or clear CIBAUD for | ... 29 lines of the commit log omitted. Produces 2 regressions: | | regressions.sum: | Running gdb:gdb.base/term.exp ... | FAIL: gdb.base/term.exp: after last resume: info terminal | FAIL: gdb.base/term.exp: post tcsetattr: info terminal Used configuration : *CI config* tcwg_gnu_native_check_gdb 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-1753. 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_gnu_native_check_gdb--master-arm-build/2297/… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/2297/… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/2297/… Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/2297/… Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/2296/… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/glibc… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=8d999a6993611d375adc…

5 months

2
2
0 0

Norwegian Air Flight Cancellation: A Quick and Simple Guide

by 8cf5i6jjvy＠bltiwd.com

If you need to cancel your Norwegian Air flight, do not worry — the process is f Airly straightforward! You can call Norwegian Air directly at 📞 1-866-284-3022. Whether you are canceling due to personal reasons, weather disruptions, or a change in plans, this guide will walk you through every step. While cancellations can be made online, calling may provide faster support and more detailed assistance. 📍 Step 1: Find Your Flight Information Before you call or go online, make sure you have the following information ready: ✅ Your booking confirmation number ✅ The name on the reservation ✅ Your flight details (departure date, destination, etc.) Having this information handy will make the process quicker, especially if you are speaking with a Norwegian Air representative at 📞 1-866-284-3022. 📞 Step 2: Call Norwegian Air Customer Support The easiest and most direct way to cancel your flight is by calling Norwegian Air customer service at 1-866-284-3022. This line is available to assist with cancellations, modifications, and refund requests. 🧑‍💼 When you call: You will be prompted to enter your confirmation number Select the option for "existing reservation" Ask to speak to a live representative if needed Pro tip: Call during off-peak hours (early mornings or late evenings) to avoid long wait times. 🌐 Step 3: Cancel Online (Alternative Option) If you prefer to cancel online, follow these steps: Go to the official Norwegian Air website Click on "My Trips" at the top of the homepage Enter your last name and confirmation code Find the reservation you want to cancel Click on “Cancel” and follow the on-screen instructions However, if you run into any issues or if your fare type does not allow online cancellations, don’t hesitate to call 1-866-284-3022 for support. 💸 Step 4: Check for Refund or Credit Eligibility Norwegian Air is a low-cost carrier, and refund policies can vary depending on the fare type. Here is a quick breakdown: 🟢 WORKS Bundle or Refundable Tickets: Eligible for a full refund 🟡 Standard Tickets: May not be refundable but can be canceled for a credit (valid for 90 days) 🔴 Basic Fare or Promo Tickets: Often non-refundable To clarify your eligibility, it is best to speak to a Vietnam representative directly at 📞 1-866-284-3022. They can explain whether you will receive a refund, a travel credit, or incur a cancellation fee. ⏱️ Step 5: Cancel Within 24 Hours (If Possible) ✅ If you booked your ticket less than 24 hours ago AND your flight is at least 7 days away, you are eligible for a full refund with no cancellation fees. To take advantage of this policy, it is strongly advised to call 1-866-284-3022 right away and notify them that you fall within the 24-hour window. 📧 Step 6: Get Confirmation of Cancellation Once your flight is canceled, make sure to: 📨 Check your email for a cancellation confirmation 💳 Verify if any refund or credit has been issued to your account 📅 Note the expiration date of any travel credit issued (typically valid for 90 days) If you have not received confirmation within a few hours, call 📞 1-866-284-3022 again to follow up and ensure your cancellation was processed correctly. 🤔 Need Help? Contact Norwegian Air Again Vietnam’s website can sometimes be tricky or limited in functionality, especially for special fares or last-minute cancellations. That is why calling customer service at 📞 1-866-284-3022 is always the most reliable option. Their agents can also assist with: Modifying your travel dates Applying travel credits Rebooking future flights Answering policy-related questions ✍️ Final Thoughts Canceling a Norwegian Air flight does not have to be stressful. Whether you are canceling online or over the phone, knowing the process and your rights can save you time and money. Always keep the Vietnam customer service number 📞 1-866-284-3022 on hand for quick assistance and peace of mind. 🧭 Quick Recap: Prepare your booking info Try canceling online or via the Vietnam app For best results, call Vietnam directly at 📞 1-866-284-3022 Check your eligibility for refunds or travel credits Always get a cancellation confirmation ✈️ Safe travels — or smooth cancellations — whichever your journey brings next!

5 months, 1 week

1
0
0 0

Re: [Linaro-TCWG-CI] v6.18-rc1-73-g3ffeb17a9a27a: Failure on aarch64

by Nathan Chancellor

On Sun, Nov 16, 2025 at 09:46:23AM +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. > > In tcwg_kernel/llvm-master-aarch64-next-allmodconfig, after: > | commit v6.18-rc1-73-g3ffeb17a9a27a > | Author: Christian Marangi <ansuelsmth(a)gmail.com> > | Date: Fri Nov 7 00:57:08 2025 +0100 > | > | pinctrl: airoha: add support for Airoha AN7583 PINs > | > | Add all the required entry to add suppot for Airoha AN7583 PINs. > | > | Where possible the same function group are used from Airoha EN7581 to > | ... 4 lines of the commit log omitted. > > Produces Failure: > | Results changed to > | # reset_artifacts: > | -10 > | # build_abe binutils: > | -9 > | # build_kernel_llvm: > | -5 > | # build_abe qemu: > | -2 > | # linux_n_obj: > | 27020 > | # First few build errors in logs: > | # 00:37:42 drivers/pinctrl/mediatek/pinctrl-airoha.c:2064:41: error: variable 'an7583_pinctrl_drive_e2_conf' is not needed and will not be emitted [-Werror,-Wunneeded-internal-declaration] https://lore.kernel.org/20251112-pinctrl-airoha-fix-an7583-drive-e2-confg-u… Cheers, Nathan

5 months, 1 week

1
0
0 0

[Linaro-TCWG-CI] glibc-2.42.9000-426-g53807741fb4: 1 regression 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.42.9000-426-g53807741fb4 | Author: Wilco Dijkstra <Wilco.Dijkstra(a)arm.com> | Date: Thu Sep 11 10:49:47 2025 -0300 | | Define __HAVE_64B_ATOMICS from compiler support | | Now that atomic builtins are used by default, we can rely on the | compiler to define when to use 64-bit atomic operations. | | ... 7 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running glibc:nss ... | FAIL: nss/tst-cancel-getpwuid_r 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-1745. 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/3193/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/3193/artifact/… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/3193/artifact/… Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/3193/artifact/… Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/3192/artifact/… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/glibc… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=53807741fb44edb8e7c0…

5 months, 1 week

2
1
0 0

[Linaro-TCWG-CI] llvmorg-22-init-14086-g046ae8553606: Failure 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 tcwg_flang_build/main-aarch64, after: | commit llvmorg-22-init-14086-g046ae8553606 | Author: Christopher Ferris <cferris1000(a)users.noreply.github.com> | Date: Mon Nov 10 14:17:23 2025 -0800 | | [scudo] Small cleanup of memory tagging code. (#166860) | | Make the systemSupportsMemoryTagging() function return even on system | that don't support memory tagging. This avoids the need to always check | if memory tagging is supported before calling th function. | ... 5 lines of the commit log omitted. Produces Failure: | Results changed to | # reset_artifacts: | -10 | # true: | 0 | # build_llvm -- clang;lld;flang;clang-tools-extra openmp : | # FAILED | # First few build errors in logs: | # 00:10:20 ld.lld: error: undefined symbol: __cxa_guard_acquire | # 00:10:20 ld.lld: error: undefined symbol: __cxa_guard_release | # 00:10:20 clang++: error: linker command failed with exit code 1 (use -v to see invocation) | | From | # reset_artifacts: | -10 | # true: | 0 | # build_llvm -- clang;lld;flang;clang-tools-extra openmp : | 1 Used configuration : tcwg_flang_build/main-aarch64 We track this bug report under https://linaro.atlassian.net/browse/LLVM-2115. 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 * https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/6073/artifac… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/6073/artifac… Current build : https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/6073/artifac… Reference build : https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/6070/artifac… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/… Full commit : https://github.com/llvm/llvm-project/commit/046ae855360614c5980d0ced0c55b5d…

5 months, 2 weeks

1
0
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain