The test fails on arm-eabi when testing with the following settings:
-mlittle-endian -mfloat-abi=hard -mcpu=cortex-a9 -mfpu=vfpv3
It only fails in the following torture option set:
-O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions
It also fails on numerous other 32-bit targets, but it depends on how
the memcpy-like loop gets vectorized and unrolled.
I hope we can live with the XPASSes.
On Apr 11, 2026, 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 thumb v8-a hard, after:
> | commit gcc-16-6952-g14cd2833b27a
> | Author: Alexandre Oliva <oliva(a)adacore.com>
> | Date: Wed Jan 21 00:30:24 2026 -0300
> |
> | testsuite: tolerate bogus warning in pr113026-1.c [PR113524]
> |
> | The bogus warning in pr113026-1.c is issued at some optimization
> | levels on various 32-bit targets.
> |
> | ... 6 lines of the commit log omitted.
> Produces 7 regressions:
> |
> | regressions.sum:
> | Running gcc:gcc.dg/torture/dg-torture.exp ...
> | XPASS: gcc.dg/torture/pr113026-1.c -O0 PR118504 (test for bogus messages, line 12)
> | XPASS: gcc.dg/torture/pr113026-1.c -O1 PR118504 (test for bogus messages, line 12)
> | XPASS: gcc.dg/torture/pr113026-1.c -O2 PR118504 (test for bogus messages, line 12)
> | XPASS: gcc.dg/torture/pr113026-1.c -O2 -flto
> | -fno-use-linker-plugin -flto-partition=none PR118504 (test for
> | bogus messages, line 12)
> | ... and 3 more
> Used configuration :
> *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb
> -march=armv8-a+simd -mfpu=auto -mfloat-abi=hard
> *configure and test flags:* --target arm-eabi --disable-multilib
> --with-mode=thumb --with-arch=armv8-a+simd
> --with-fpu=crypto-neon-fp-armv8 --with-float=hard
> --target_board=-mthumb/-march=armv8-a+simd/-mfpu=auto/-mfloat-abi=hard
> qemu_cpu=any
> We track this bug report under
> https://linaro.atlassian.net/browse/GNU-1870. 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
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_v8a_h…
> The full lists of regressions and improvements as well as configure
> and make commands are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_v8a_h…
> The list of [ignored] baseline and flaky failures are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_v8a_h…
> Current build :
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_v8a_h…
> Reference build :
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_v8a_h…
> 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
--
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!
Hi!
On 4/3/26 08:06, ci_notify--- via Gcc-regression wrote:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In aarch64 native, after:
> | commit gcc-16-8401-g71033b1dfbd1
> | Author: Roger Sayle <roger(a)nextmovesoftware.com>
> | Date: Wed Apr 1 23:54:50 2026 +0100
> |
> | PR target/123238: VCOND_MASK regression on aarch64.
> |
> | This patch fixes the regression PR target/123238 on aarch64, using the
> | changes to aarch64's aarch64_rtx_costs proposed by Tamar Christina.
> |
> | ... 38 lines of the commit log omitted.
>
> Produces 1 regression:
> |
> | regressions.sum:
> | Running gcc:gcc.target/aarch64/aarch64.exp ...
> | FAIL: gcc.target/aarch64/pr123238.c scan-assembler-not not
>
This was fixed by Andrew in:
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=9c694b3ecd0eb5308e85a0eac69c4…
Thanks,
Christophe
> Used configuration :
> *CI config* tcwg_gcc_check aarch64-linux-gnu
> *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu--disable-multilib --enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1868. 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
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
> The full lists of regressions and improvements as well as configure and make commands are in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
> The list of [ignored] baseline and flaky failures are in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> 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
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hi,
Probably these errors are false detections caused by precision errors in floating-point arithmetic. Please ignore the mail. We'll update the tests.
I apologize for the false detection.
Best regards,
Yasuyuki Ohno
Software Development Div.,
Advanced Technology Development Unit,
Fujitsu Research, Fujitsu Limited, JAPAN.
________________________________
差出人: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
送信: 2026 年 4 月 12 日 (日曜日) 17:45
宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com>
Cc: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>; a.bataev(a)outlook.com <a.bataev(a)outlook.com>
件名: [Linaro-TCWG-CI] llvmorg-23-init-11166-g8ac9461e48e0: 1 regression 1 fix on aarch64
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-11166-g8ac9461e48e0
| Author: Alexey Bataev <a.bataev(a)outlook.com>
| Date: Sat Apr 11 08:18:36 2026 -0400
|
| [SLP] Reject 2-element vectorization when vector inst count exceeds scalar
|
| The LLVM cost model uses integer-valued throughput costs which cannot
| represent fractional costs. For 2-element vectors, this rounding can
| make vectorization appear profitable when it actually produces more
| ... 15 lines of the commit log omitted.
Produces 1 regression 1 fix:
|
| regressions.sum:
| Running test-suite:Fujitsu/C/0121 ...
| FAIL: test-suite :: Fujitsu/C/0121/Fujitsu-C-0121_0259.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/0640 ...
| FAIL: test-suite :: Fujitsu/Fortran/0640/Fujitsu-Fortran-0640_0216.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-2210. 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
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
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/8ac9461e48e024448a2b6493b7c5b50…
Hi there,
I got a notification about a build failure on the flang-arm64-windows-msvc buildbot earlier today, I’ve included the original email below.
The commit in question that caused the failure added some new intrinsics, touching some tablegen files, which then caused some tests for unrelated intrinsics to fail: https://github.com/llvm/llvm-project/commit/9ba774566e27b76b9c7c2b2ddd108c1…https://lab.llvm.org/buildbot/#/builders/207/builds/15865
But the buildbot went back to green in https://lab.llvm.org/buildbot/#/builders/207/builds/15869 when another PR changed some other tablegen files in the llvm project. I didn’t revert or commit any fixes in the meantime.
Is there maybe some issue with the build cache and how tablegen files interact with it? Just thought I’d flag this to you anyway.
Many thanks
Luke
> Begin forwarded message:
>
> From: llvm.buildmaster(a)lab.llvm.org
> Subject: ☠ Buildbot (LLVM Buildbot): flang-arm64-windows-msvc - failed test (failure) (main)
> Date: 9 April 2026 at 16:03:07 GMT+8
> To: "Luke Lau" <luke(a)igalia.com>, "Nikita Popov" <npopov(a)redhat.com>
> Cc: llvm.buildmaster(a)lab.llvm.org
> Reply-To: llvm.buildmaster(a)lab.llvm.org
>
> The Buildbot has detected a new failure on builder flang-arm64-windows-msvc while building llvm.
>
> Full details are available at:
> https://lab.llvm.org/buildbot/#/builders/207/builds/15865
>
> Worker for this Build: linaro-armv8-windows-msvc-01
> Blamelist:
> Luke Lau <luke(a)igalia.com>,
> Nikita Popov <npopov(a)redhat.com>
>
> BUILD FAILED: failed test (failure)
>
> Step 6 (test-build-unified-tree-check-mlir) failure: test (failure)
> ******************** TEST 'MLIR :: mlir-runner/test-expand-math-approx.mlir' FAILED ********************
> Exit Code: 2
>
> Command Output (stdout):
> --
> # RUN: at line 1
> c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir-opt.exe C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\llvm-project\mlir\test\mlir-runner\test-expand-math-approx.mlir -pass-pipeline="builtin.module(func.func(math-expand-ops),convert-vector-to-scf,convert-scf-to-cf,convert-vector-to-llvm,convert-to-llvm,reconcile-unrealized-casts)" | c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir-runner.exe -e main -entry-point-result=void -O0 -shared-libs=C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir_c_runner_utils.dll -shared-libs=C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir_runner_utils.dll -shared-libs=C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir_float16_utils.dll | c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\filecheck.exe C:\Users\tcwg\llvm-worker\flang-arm64-windows-ms
> vc\llvm-project\mlir\test\mlir-runner\test-expand-math-approx.mlir
> # executed command: 'c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir-opt.exe' 'C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\llvm-project\mlir\test\mlir-runner\test-expand-math-approx.mlir' '-pass-pipeline=builtin.module(func.func(math-expand-ops),convert-vector-to-scf,convert-scf-to-cf,convert-vector-to-llvm,convert-to-llvm,reconcile-unrealized-casts)'
> # executed command: 'c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir-runner.exe' -e main -entry-point-result=void -O0 '-shared-libs=C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir_c_runner_utils.dll' '-shared-libs=C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir_runner_utils.dll' '-shared-libs=C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir_float16_utils.dll'
> # .---command stderr------------
> # | LLVM ERROR: Cannot select: intrinsic %llvm.aarch64.neon.ushl
> # | PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace and instructions to reproduce the bug.
> # | Stack dump:
> # | 0. Program arguments: c:\\users\\tcwg\\llvm-worker\\flang-arm64-windows-msvc\\build\\bin\\mlir-runner.exe -e main -entry-point-result=void -O0 -shared-libs=C:\\Users\\tcwg\\llvm-worker\\flang-arm64-windows-msvc\\build\\bin\\mlir_c_runner_utils.dll -shared-libs=C:\\Users\\tcwg\\llvm-worker\\flang-arm64-windows-msvc\\build\\bin\\mlir_runner_utils.dll -shared-libs=C:\\Users\\tcwg\\llvm-worker\\flang-arm64-windows-msvc\\build\\bin\\mlir_float16_utils.dll
> # | 1. Running pass 'Function Pass Manager' on module 'LLVMDialectModule'.
> # | 2. Running pass 'AArch64 Instruction Selection' on function '@"func_roundeven32$vector"'
> # | Exception Code: 0xC000001D
> # | #0 0x00007ff674c89e4c mlir::detail::FallbackTypeIDResolver::registerImplicitTypeID(class llvm::StringRef) (c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir-runner.exe+0x309e4c)
> # | #1 0x00007ffec74aae50 (C:\WINDOWS\System32\ucrtbase.dll+0x7ae50)
> # | #2 0xa25cfffec74aba5c
> # `-----------------------------
> # error: command failed with exit status: 0xc000001d
> # executed command: 'c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\filecheck.exe' 'C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\llvm-project\mlir\test\mlir-runner\test-expand-math-approx.mlir'
> # .---command stderr------------
> # | FileCheck error: '<stdin>' is empty.
> # | FileCheck command line: c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\filecheck.exe C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\llvm-project\mlir\test\mlir-runner\test-expand-math-approx.mlir
> # `-----------------------------
> # error: command failed with exit status: 2
>
> --
>
> ********************
>
>
> Sincerely,
> LLVM Buildbot
>
This is https://gcc.gnu.org/bugzilla/show_bug.cgi?id=124828.
On Fri, Apr 10, 2026 at 1:15 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 aarch64 native, after:
> | commit gcc-16-8510-g395e5cef29d9
> | Author: Tomasz Kamiński <tkaminsk(a)redhat.com>
> | Date: Wed Apr 1 14:32:21 2026 +0200
> |
> | libstdc++: Export explicit instantiations for C++20 members of
> std::string
> |
> | The C++20 standard added new starts_with and ends_with members to
> | std::basic_string, which were not previously instantiated in the
> library.
> | This meant that the extern template declarations had to be
> disabled for
> | ... 31 lines of the commit log omitted.
>
> Produces 1 regression:
> |
> | regressions.sum:
> | Running g++:g++.dg/lto/lto.exp ...
> | FAIL: g++.dg/lto/20091022-2
> cp_lto_20091022-2_0.o-cp_lto_20091022-2_0.o link, -O3 -flto -Winline
>
> Used configuration :
> *CI config* tcwg_gcc_check aarch64-linux-gnu
> *configure and test flags:* none, autodetected on
> aarch64-unknown-linux-gnu--disable-multilib --enable-fix-cortex-a53-835769
> --enable-fix-cortex-a53-843419 --with-arch=armv8-a
>
> We track this bug report under
> https://linaro.atlassian.net/browse/GNU-1869. 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
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
> The full lists of regressions and improvements as well as configure and
> make commands are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
> The list of [ignored] baseline and flaky failures are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> Current build :
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
> Reference build :
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> 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
>
On Thu, 2 Apr 2026 at 06:27, <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 aarch64 native, after:
> | commit gcc-16-8385-gc9525a790291
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Mon Mar 30 12:13:39 2026 +0100
> |
> | libstdc++: Rename saturation arithmetic for C++26 (P4052R0)
> |
> | Last week in Croydon we approved P4052R0 to rename std::add_sat etc. for
> | C++26
> |
> | ... 16 lines of the commit log omitted.
>
> Produces 3 regressions:
> |
> | regressions.sum:
> | Running g++:g++.dg/modules/modules.exp ...
> | FAIL: g++.dg/modules/compile-std1.C -std=c++26 (test for excess errors)
> | FAIL: g++.dg/modules/compile-std1.C module-cmi std (gcm.cache/std.gcm)
> | FAIL: g++.dg/modules/compile-std1.C module-cmi std.compat (gcm.cache/std.compat.gcm)
>
> Used configuration :
> *CI config* tcwg_gcc_check aarch64-linux-gnu
> *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu--disable-multilib --enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1867. Please let us know if you have a fix.
It's fixed now
>
> 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
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
> The full lists of regressions and improvements as well as configure and make commands are in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
> The list of [ignored] baseline and flaky failures are in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> 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
Hi,
These errors are caused by incorrect test programs. Please ignore the mail. We'll update the tests.
I apologize for the false detection.
Best regards,
Shunsuke Watanabe
Software Development Div.,
Advanced Technology Development Unit,
Fujitsu Research, Fujitsu Limited, JAPAN.
-----Original Message-----
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: Wednesday, April 1, 2026 2:37 AM
To: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com
Cc: aidengrossman(a)google.com; maxim.kuvyrkov(a)linaro.org
Subject: [Linaro-TCWG-CI] llvmorg-23-init-9791-g12319b373a5f: 1 regression on aarch64
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-9791-g12319b373a5f
| Author: Aiden Grossman <aidengrossman(a)google.com>
| Date: Mon Mar 30 16:34:37 2026 -0700
|
| [Clang] More aggressively mark this* dead_on_return in destructors (#183347)
|
| Now also mark the this pointer dead_on_return for classes with a
| non-zero number of base classes. We saw a limited number of failures
| internally due to this change, so it doesn't seem like there are too
| ... 1 lines of the commit log omitted.
Produces 1 regression:
|
| regressions.sum:
| Running test-suite:Fujitsu/C++/0032 ...
| FAIL: test-suite :: Fujitsu/C++/0032/Fujitsu-C++-0032_1052.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-2208. 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
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
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/12319b373a5f4b36c09165ed7f8e967…
I think this is the same issue as reported in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=124124,
that was addressed by:
commit r16-7911-g3a41229f92022bfb388911854d597721fce76714
<https://gcc.gnu.org/cgit/gcc/commit/?id=3a41229f92022bfb388911854d597721fce…>
Author: Tomasz KamiÅski <tkaminsk(a)redhat.com>
Date: Thu Mar 5 08:57:24 2026 +0100
libstdc++: Fix atomic/cons/zero_padding.cc test for arm-none-eabi
[PR124124 <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=124124>]
The test uses dg-require-atomic-cmpxchg-word that checks if atomic compare
exchange is available for pointer sized integers, and then test types that
are eight bytes in size. This causes issue for targets for which pointers
are four byte and libatomic is not present, like arm-none-eabi.
This patch addresses by using short member in TailPadding and MidPadding,
instead of int. This reduces the size of types to four bytes, while keeping
padding bytes present.
PR libstdc++/124124
<https://gcc.gnu.org/bugzilla/show_bug.cgi?id=124124>
libstdc++-v3/ChangeLog:
* testsuite/29_atomics/atomic/cons/zero_padding.cc: Limit size of
test types to four bytes.
On Sun, Mar 22, 2026 at 9:01 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-7434-g6b550d69fe7c
> | Author: Tomasz Kamiński <tkaminsk(a)redhat.com>
> | Date: Thu Jan 29 18:14:47 2026 +0100
> |
> | libstdc++: Allow constant initialization of std::atomic of types
> with padding [PR123875]
> |
> | Currently for the types T that contains padding bits,
> std::atomic<T>(T)
> | constructor was not usable at compile-time in C++14 or later
> modes. This
> | regression caused by use of __builtin_clear_padding introduced in
> | ... 49 lines of the commit log omitted.
>
> Produces 2 regressions:
> |
> | regressions.sum:
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL: 29_atomics/atomic/cons/static_zero_padding.cc -std=gnu++20 (test
> for excess errors)
> | UNRESOLVED: 29_atomics/atomic/cons/static_zero_padding.cc -std=gnu++20
> compilation failed to produce executable
>
> 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-1865. 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
Hi all,
the linaro CI reported test errors for aarch64 targets. I figured that for
aarch64 on linux the compile flags -pthread and -lrt are needed to link
caf_shmem and produce an executable. The attached patch addresses this by
special case for aarch64-*-linux* similiar to freebsd.
Regtested ok on aarch64-unknown-linux-gnu (cfarm185) and x86_64-linux-gnu /
F43. Ok for master?
Regards,
Andre
On Thu, 12 Mar 2026 04:46:24 +0000 (UTC)
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-7727-gaa09298cb017
> | Author: Andre Vehreschild <vehre(a)gcc.gnu.org>
> | Date: Wed Jun 18 09:26:22 2025 +0200
> |
> | Fortran: Enable coarray tests for multi image use [PR88076]
> |
> | Change some of regression tests to run on single and multiple images.
> | Add some new tests.
> |
> | ... 29 lines of the commit log omitted.
>
> Produces 157 regressions:
> |
> | regressions.sum:
> | Running gfortran:gfortran.dg/coarray/caf.exp ...
> | FAIL: gfortran.dg/coarray/alloc_comp_1.f90 -fcoarray=lib -O2
> -lcaf_shmem (test for excess errors) | UNRESOLVED:
> gfortran.dg/coarray/alloc_comp_1.f90 -fcoarray=lib -O2 -lcaf_shmem
> compilation failed to produce executable | FAIL:
> gfortran.dg/coarray/alloc_comp_10.f90 -fcoarray=lib -O2 -lcaf_shmem (test
> for excess errors) | UNRESOLVED: gfortran.dg/coarray/alloc_comp_10.f90
> -fcoarray=lib -O2 -lcaf_shmem compilation failed to produce executable |
> ... and 153 more
>
> 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-1860.
> 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/26…
> 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/26…
> The list of [ignored] baseline and flaky failures are in
> *
> https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/26…
>
> Current build :
> https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/26…
> Reference build :
> https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/26…
>
> 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
--
Andre Vehreschild * Email: vehre ad gmx dot de
Hi,
On 3/11/26 04:19, ci_notify--- via Gcc-regression 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-7569-gc94fdc1590d
> | Author: Torbjörn SVENSSON <torbjorn.svensson(a)foss.st.com>
> | Date: Tue Feb 17 16:08:58 2026 +0100
> |
> | testsuite: arm: Use effective-target for aes-fuse-[12].c
> |
> | gcc/testsuite/ChangeLog:
> |
> | * gcc.target/arm/aes-fuse-1.c: Use effective-target
> | ... 6 lines of the commit log omitted.
>
> Produces 2 regressions:
> |
> | regressions.sum:
> | Running gcc:gcc.target/arm/arm.exp ...
> | ERROR: gcc.target/arm/aes-fuse-1.c: unknown effective target keyword `arm_cpu_cortex_a53' for " dg-require-effective-target 3 arm_cpu_cortex_a53 "
> | ERROR: gcc.target/arm/aes-fuse-2.c: unknown effective target keyword `arm_cpu_cortex_a53' for " dg-require-effective-target 3 arm_cpu_cortex_a53 "
>
I believe this was fixed by
https://gcc.gnu.org/pipermail/gcc-patches/2026-March/709997.htmlhttps://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=41aba0b725e942f65d59b719c…
Thanks,
Christophe
> 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-1859. 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/2652/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/2652/a…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/2652/a…
>
> Current build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/2652/a…
> Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/2649/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
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hi,
On Sun, Mar 8, 2026 at 2:21 PM ci_notify--- via Gcc-regression <
gcc-regression(a)gcc.gnu.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-7439-g1ced019ad9d
> | Author: Alice Carlotti <alice.carlotti(a)arm.com>
> | Date: Wed Jan 14 13:48:35 2026 +0000
> |
> | aarch64: Disable shrink-wrap for locally-streaming functions [PR
> 123624]
> |
> | The meaning of poly_int values changes depending on whether we are
> in
> | streaming or non-streaming mode, but this dependency is not
> explicitly
> | tracked. Locally-streaming functions can change streaming state
> in the
> | ... 17 lines of the commit log omitted.
>
> Produces 4 regressions:
> |
> | regressions.sum:
> | Running gcc:gcc.target/aarch64/sme/aarch64-sme.exp ...
> | UNRESOLVED: gcc.target/aarch64/sme/sme-shrinkwrap.c
> check-function-bodies bar
> | UNRESOLVED: gcc.target/aarch64/sme/sme-shrinkwrap.c
> check-function-bodies baz
> | UNRESOLVED: gcc.target/aarch64/sme/sme-shrinkwrap.c
> check-function-bodies foo
> | FAIL: gcc.target/aarch64/sme/sme-shrinkwrap.c execution test
>
> 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-1856. Please let us know if you
> have a fix.
>
This is hopefully fixed by
https://gcc.gnu.org/pipermail/gcc-patches/2026-March/710145.htmlhttps://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=24d41d10f28bfae6461003994…
Thanks,
Christophe
>
> 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/26…
> 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/26…
> The list of [ignored] baseline and flaky failures are in
> *
> https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/26…
>
> Current build :
> https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/26…
> Reference build :
> https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/26…
>
> 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
>
Hi,
On 3/5/26 15: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-m55 hard, after:
> | commit gcc-16-7262-gf7f2b73b9c1e
> | Author: Christophe Lyon <christophe.lyon(a)arm.com>
> | Date: Tue Feb 3 13:07:10 2026 +0000
> |
> | testsuite: arm: Make arm_neon_ok_nocache consistent with other effective-targets
> |
> | A recent patch updated arm_neon_ok_nocache with an improved list of
> | flags to try, but was not consistent with
> | arm_v8_3a_complex_neon_ok,_nocache arm_v8_2a_fp16_neon_ok_nocache,
> | ... 14 lines of the commit log omitted.
>
> Produces 2 regressions 2 fixes:
> |
> | regressions.sum:
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL: experimental/simd/pr109261_constexpr_simd.cc -mcpu=unset -march=armv7-a+simd -mfpu=auto -ffast-math -O2 -Wno-psabi (test for excess errors)
> | FAIL: experimental/simd/pr115454_find_last_set.cc -mcpu=unset -march=armv7-a+simd -mfpu=auto -ffast-math -O2 -Wno-psabi (test for excess errors)
> |
> | fixes.sum:
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL: experimental/simd/pr109261_constexpr_simd.cc -mfloat-abi=softfp -mcpu=unset -march=armv7-a+simd -mfpu=auto -ffast-math -O2 -Wno-psabi (test for excess errors)
> | FAIL: experimental/simd/pr115454_find_last_set.cc -mfloat-abi=softfp -mcpu=unset -march=armv7-a+simd -mfpu=auto -ffast-math -O2 -Wno-psabi (test for excess errors)
>
This does not look like a "real" regression: the same tests are still
failing, using different options.
Thanks,
Christophe
> 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-1853. 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
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hi,
Probably these errors are false detections caused by precision errors in floating-point arithmetic. Please ignore the mail. We'll update the tests.
I apologize for the false detection.
Best regards,
Shunsuke Watanabe
Software Development Div.,
Advanced Technology Development Unit,
Fujitsu Research, Fujitsu Limited, JAPAN.
-----Original Message-----
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: Friday, March 6, 2026 6:40 AM
To: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com
Cc: flo(a)fhahn.com; maxim.kuvyrkov(a)linaro.org
Subject: [Linaro-TCWG-CI] llvmorg-23-init-5844-g320220e48b8f: 1 regression on aarch64
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_vla, after:
| commit llvmorg-23-init-5844-g320220e48b8f
| Author: Florian Hahn <flo(a)fhahn.com>
| Date: Sun Mar 1 16:07:05 2026 +0000
|
| [VPlan] Support arbitrary predicated early exits. (#182396)
|
| This removes the restriction requiring a single predicated early exit.
| Using MaskedCond, we only combine early-exit conditions with block
| masks from non-exiting control flow.
| ... 10 lines of the commit log omitted.
Produces 1 regression:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0681 ...
| FAIL: test-suite :: Fujitsu/Fortran/0681/Fujitsu-Fortran-0681_0038.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=scalable -mllvm -scalable-vectorization=preferred -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -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-2187. 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_vla-build…
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_vla-build…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
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/320220e48b8f1054ce7a37c8b2a5283…
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In binutils_build master-arm, after:
| commit binutils-2_41-release-10003-gf1a664fa55a
| Author: Alan Modra <amodra(a)gmail.com>
| Date: Tue Mar 3 10:20:54 2026 +1030
|
| Define BFD_ASAN to detect asan
Produces Failure:
| Results changed to
| # reset_artifacts:
| -10
| # true:
| 0
| # build_abe binutils:
| # FAILED
| # First few build errors in logs:
| # 00:02:40 ./bfd.h:164:50: error: missing binary operator before token
| # 00:02:41 make[4]: *** [Makefile:1766: archive.lo] Error 1
| # 00:02:41 make[3]: *** [Makefile:1946: all-recursive] Error 1
| # 00:02:41 make[2]: *** [Makefile:1332: all] Error 2
| # 00:02:41 make[1]: *** [Makefile:3138: all-bfd] Error 2
| # 00:02:41 make: *** [Makefile:1033: all] Error 2
|
| From
| # reset_artifacts:
| -10
| # true:
| 0
| # build_abe binutils:
| 1
Used configuration :
*CI config* tcwg_binutils_build 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-1850. 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_binutils_build--master-arm-build/3078/artifa…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_binutils_build--master-arm-build/3078/artifa…
Current build : https://ci.linaro.org/job/tcwg_binutils_build--master-arm-build/3078/artifa…
Reference build : https://ci.linaro.org/job/tcwg_binutils_build--master-arm-build/3076/artifa…
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=f1a664fa55a9e…
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 newlib-4.6.0-5-g4356ccd02c
| Author: Thomas Wolff <towo(a)towo.net>
| Date: Mon Feb 2 00:00:00 2026 +0000
|
| towupper/towlower: handle Turkic language special casing
|
| For case conversion, Unicode has a standard mapping and a separate
| list of mapping rules for special cases (file SpecialCasing.txt),
| some of which are also language-dependent (as configured via locale).
| ... 10 lines of the commit log omitted.
Produces 34 regressions:
|
| regressions.sum:
| Running libstdc++:libstdc++-dg/conformance.exp ...
| FAIL: 22_locale/ctype/is/wchar_t/1.cc -std=gnu++20 execution test
| FAIL: 22_locale/ctype/is/wchar_t/11740.cc -std=gnu++20 execution test
| FAIL: 22_locale/ctype/to/wchar_t/1.cc -std=gnu++20 execution test
| FAIL: 22_locale/time_get/get/wchar_t/1.cc -std=gnu++20 execution test
| ... and 30 more
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-1849. 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/newli…
Full commit : https://sourceware.org/git/?p=newlib-cygwin.git;a=commitdiff;h=4356ccd02c9c…
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.
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…
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
[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…
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
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