On 7/4/26 18:40, ci_notify(a)linaro.org wrote:
> /usr/bin/ld: error: libcommon.a: file too short
I don't understand this. How can any patch to the Fortran front end
(much less a completely trivial one) affect libcommon.a? If that file
was truncated maybe it was a transient disk-full or file system error?
-Sandra
On 05/07/2026 02:18, 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 simplebootstrap_build master-aarch64-bootstrap, after:
> | 7 patches in gcc
> | Patchwork URL: https://patchwork.sourceware.org/patch/138418
> | 9535bc30d4a [PATCH v3 7/8] MAINTAINERS: generate from MAINTAINERS.yml
> | 4a13feeed49 [PATCH v3 6/8] MAINTAINERS.yml: Add libcpp to all C and C++ maintainer's roles
> | 246b6c1ec06 [PATCH v3 5/8] MAINTAINERS.yml: Handle libgrust explicitly
> | 024b571b710 [PATCH v3 4/8] MAINTAINERS.yml: Restore James Norris' email address
> | f13d5705819 [PATCH v3 3/8] MAINTAINERS.yml: Correct Martin Liška's name
> | ... and 2 more patches in gcc
> | ... applied on top of baseline commit:
> | e365e5473a8 libgcc, Darwin: Fix missing prerequisite [PR123976].
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | # FAILED
> | # First few build errors in logs:
> | # 01:34:20 make[3]: [Makefile:1881: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored)
> | # 01:34:20 make[3]: [Makefile:1882: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored)
> | # 01:42:17 make[8]: [Makefile:868: stamp-modules-bits] Error 1 (ignored)
> | # 02:02:57 make[3]: *** [Makefile:4629: io/intrinsics.lo] Error 1
> | # 02:02:57 make[2]: *** [Makefile:1882: all] Error 2
> | # 02:02:57 make[1]: *** [Makefile:21363: all-target-libgfortran] Error 2
> | # 02:02:57 make: *** [Makefile:1142: all] Error 2
> |
This report is also bogus. The patch doesn't go anywhere near the main compiler or library sources.
R.
> | From
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | 1
>
> Used configuration :
> *CI config* tcwg_simplebootstrap_build master-aarch64-bootstrap
> *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
> * http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-aarch64-b…
> The full lists of regressions and improvements as well as configure and make commands are in
> * http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-aarch64-b…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-aarch64-b…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-aarch64-b…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
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.
On 04/07/2026 04:12, 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 simplebootstrap_build master-aarch64-bootstrap, after:
> | 8 patches in gcc
> | Patchwork URL: https://patchwork.sourceware.org/patch/138422
> | 16c863d8c02 [PATCH v3 8/8] MAINTAINERS: Add a script to create a new entry in the mainainers data
> | ff60e686f8f [PATCH v3 7/8] MAINTAINERS: generate from MAINTAINERS.yml
> | d3f4eba32fd [PATCH v3 6/8] MAINTAINERS.yml: Add libcpp to all C and C++ maintainer's roles
> | 403583056ec [PATCH v3 5/8] MAINTAINERS.yml: Handle libgrust explicitly
> | 3389564de59 [PATCH v3 4/8] MAINTAINERS.yml: Restore James Norris' email address
> | ... and 3 more patches in gcc
> | ... applied on top of baseline commit:
> | a20f4528f3a tree-optimization/122569 - recognize CLZ via isolated MSB DeBruijn lookup
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | # FAILED
> | # First few build errors in logs:
> | # 00:09:12 make[3]: [Makefile:1881: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored)
> | # 00:09:12 make[3]: [Makefile:1882: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored)
> | # 00:59:19 make[3]: [Makefile:1881: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored)
> | # 00:59:19 make[3]: [Makefile:1882: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored)
> | # 01:16:13 make[3]: [Makefile:1881: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored)
> | # 01:16:13 make[3]: [Makefile:1882: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored)
> | # 01:17:22 make[6]: *** [Makefile:631: libstdc++fsconvenience.la] Error 1
> | # 01:17:22 make[6]: *** [Makefile:628: libstdc++fs.la] Error 1
> | # 01:17:22 make[5]: *** [Makefile:802: all-recursive] Error 1
> | # 01:17:22 make[4]: *** [Makefile:580: all-recursive] Error 1
> |
Nothing in this patch could possibly produce the above error, so it must be due to the baseline commit being broken, or some other problem with the CI bot.
> | From
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | 1
>
> Used configuration :
> *CI config* tcwg_simplebootstrap_build master-aarch64-bootstrap
> *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
> * http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-aarch64-b…
> The full lists of regressions and improvements as well as configure and make commands are in
> * http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-aarch64-b…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-aarch64-b…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-aarch64-b…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
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.
This doesn't seem right given the patch. All tests passed when I tested it locally on aarch64 using two different toolchains.
________________________________________
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: 05 July 2026 12:02 PM
To: Yury Khrustalev
Cc: Yury Khrustalev
Subject: [Linaro-TCWG-CI] glibc patch #138079: 2 regressions 97 fixes on aarch64
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In glibc_check master-aarch64, after:
| glibc patch https://patchwork.sourceware.org/patch/138079
| Author: Yury Khrustalev <yury.khrustalev(a)arm.com>
| Date: Mon Jun 29 17:37:22 2026 +0100
|
| [PATCH 1/1] aarch64: compile malloc ifuncs conditionally
|
| On AArch64, ifuncs are used for malloc functions by default.
|
| The code for resolvers in sysdeps/aarch64/multiarch/malloc-ifuncs.c
| ... 5 lines of the commit log omitted.
| ... applied on top of baseline commit:
| d109f366ce build-many-glibcs.py: Update Linux kernel version to 7.1
Produces 2 regressions 97 fixes:
|
| regressions.sum:
| Running glibc:nptl ...
| FAIL: nptl/tst-fopen-threaded
| Running glibc:posix ...
| FAIL: posix/tst-affinity-static
|
| fixes.sum:
| Running glibc:debug ...
| FAIL: debug/tst-fortify-syslog
| Running glibc:dirent ...
| FAIL: dirent/tst-readdir-long
| ... and 108 more
Used configuration :
*CI config* tcwg_glibc_check 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 *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-aarch64-precommit/b…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-aarch64-precommit/b…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-aarch64-precommit/b…
Current build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-aarch64-precommit/b…
Reference build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-aarch64-build/build…
Warning: we do not enable maintainer-mode nor automatically update
generated files, which may lead to failures if the patch modifies the
master files.
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.
Thanks for reporting this.
This is expected regression due to possible bug in Valgrind. For details, see:
https://bugs.kde.org/show_bug.cgi?id=522497https://inbox.sourceware.org/libc-alpha/cover.1782766548.git.fweimer@redhat…
Thanks,
Yury
________________________________________
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: 05 July 2026 10:50 AM
To: Yury Khrustalev
Cc: Yury Khrustalev
Subject: [Linaro-TCWG-CI] glibc patch #138207: 1 regression 97 fixes on aarch64
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In glibc_check master-aarch64, after:
| glibc patch https://patchwork.sourceware.org/patch/138207
| Author: Yury Khrustalev <yury.khrustalev(a)arm.com>
| Date: Wed Jul 1 14:16:17 2026 +0100
|
| [PATCH] aarch64: Fail early if malloc ifunc resolver is called incorrectly
|
| This patch adds simple check that validates the call to ifunc resolver
| for the malloc function. If resolver is called correctly, it must
| receive at least 1 argument that is equal to the value of AT_HWCAP
| ... 6 lines of the commit log omitted.
| ... applied on top of baseline commit:
| d109f366ce build-many-glibcs.py: Update Linux kernel version to 7.1
Produces 1 regression 97 fixes:
|
| regressions.sum:
| Running glibc:elf ...
| FAIL: elf/tst-valgrind-smoke
|
| fixes.sum:
| Running glibc:debug ...
| FAIL: debug/tst-fortify-syslog
| ... and 110 more
Used configuration :
*CI config* tcwg_glibc_check 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 *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-aarch64-precommit/b…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-aarch64-precommit/b…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-aarch64-precommit/b…
Current build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-aarch64-precommit/b…
Reference build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-aarch64-build/build…
Warning: we do not enable maintainer-mode nor automatically update
generated files, which may lead to failures if the patch modifies the
master files.
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.
On Thu, 2 Jul 2026 at 23:45, <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-m33 hard, after:
> | commit gcc-17-1905-g70e630b6d29b
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Thu Jun 25 12:59:04 2026 +0100
> |
> | libstdc++: Update feature test macros and tests for C++29
> |
> | With r17-1595-g0c5c6249a2e9a7 G++ supports -std=c++29 so update our
> | feature test macro generation and testsuite to know about it.
> |
> | ... 19 lines of the commit log omitted.
>
> Produces 5 regressions 5 fixes:
> |
> | regressions.sum:
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL: 19_diagnostics/stacktrace/entry.cc -std=gnu++29 execution test
> | FAIL: 19_diagnostics/stacktrace/output.cc -std=gnu++29 execution test
> | FAIL: 19_diagnostics/stacktrace/stacktrace.cc -std=gnu++29 execution test
> | FAIL: 27_io/print/2.cc -std=gnu++29 (test for excess errors)
> | ... and 1 more
> |
> | fixes.sum:
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL: 19_diagnostics/stacktrace/entry.cc -std=gnu++26 execution test
> | FAIL: 19_diagnostics/stacktrace/output.cc -std=gnu++26 execution test
> | FAIL: 19_diagnostics/stacktrace/stacktrace.cc -std=gnu++26 execution test
> | FAIL: 27_io/print/2.cc -std=gnu++26 (test for excess errors)
> | ... and 1 more
>
> Used configuration :
> *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv8-m.main+dsp+fp -mtune=cortex-m33 -mfloat-abi=hard -mfpu=auto
> *configure and test flags:* --target arm-eabi --disable-multilib --with-mode=thumb --with-cpu=cortex-m33 --with-float=hard --target_board=-mthumb/-march=armv8-m.main+dsp+fp/-mtune=cortex-m33/-mfloat-abi=hard/-mfpu=auto qemu-cpu=cortex-m33
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1942. (Require Linaro login) Please let us know if you have a fix.
This isn't really a regression, it's because the tests switched from
being run with -std=gnu++26 to -std=gnu++29, but they still FAIL the
same way.
>
> 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_m33_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_m33_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_m33_h…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m33_h…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m33_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
I think this is a misattribution of the failure. #203481 is a change
of the CMake build system, it does not change anything functional in
the flang compiler. #203481 had a build problem which was fixed in
#204438. But since Flang built successfully, it cannot be the problem
of that CI problem.
Michael
Am Fr., 19. Juni 2026 um 13:56 Uhr schrieb <ci_notify(a)linaro.org>:
>
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In tcwg_flang_test/main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays, after:
> | commit llvmorg-23-init-19659-g3fee6e5ab45d
> | Author: Michael Kruse <llvm-project(a)meinersbur.de>
> | Date: Wed Jun 17 16:13:40 2026 +0200
> |
> | [Flang] Add mock flang driver (#203481)
> |
> | Add a mock driver to pass CMake's compiler introspection for
> | CMake_Fortran_COMPILER. It's purpose is to not having to build the full
> | flang compiler for the runtimes-configure phase in
> | ... 59 lines of the commit log omitted.
>
> Produces 18533 regressions:
> |
> | regressions.sum:
> | Running test-suite:Fujitsu/Fortran/0004 ...
> | NOEXE: test-suite :: Fujitsu/Fortran/0004/Fujitsu-Fortran-0004_0001.test
> | NOEXE: test-suite :: Fujitsu/Fortran/0004/Fujitsu-Fortran-0004_0002.test
> | Running test-suite:Fujitsu/Fortran/0005 ...
> | NOEXE: test-suite :: Fujitsu/Fortran/0005/Fujitsu-Fortran-0005_0001.test
> | ... and 19173 more
> | # "NOEXE" means : the test program cannot be compiled
>
> 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 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG -fstack-arrays" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite"
>
> We track this bug report under https://linaro.atlassian.net/browse/LLVM-2235. (Require Linaro login) 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-O3-neoverse_v1…
> 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-O3-neoverse_v1…
> The list of [ignored] baseline and flaky failures are in
> * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1…
>
> Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1…
>
> 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/3fee6e5ab45d1d352f995ae4eafa510…
--
Tardyzentrismus verboten!
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In aarch64 native, after:
| commit glibc-2.43.9000-403-g9ed3576e61f
| Author: Yury Khrustalev <yury.khrustalev(a)arm.com>
| Date: Tue May 26 11:19:53 2026 +0100
|
| malloc: aarch64: Add ifuncs for malloc functions
|
| Introduce ifuncs and resolvers for functions pertinent to the
| malloc interface on the AArch64 target: malloc, calloc, free,
| realloc, memalign, valloc, pvalloc, posix_memalign, aligned_alloc,
| ... 13 lines of the commit log omitted.
Produces 118 regressions:
|
| regressions.sum:
| Running gdb:gdb.base/call-strs.exp ...
| FAIL: gdb.base/call-strs.exp: call str_func("a","b","c","d","e","f","g")
| FAIL: gdb.base/call-strs.exp: print str_func("a","b","c","d","e","f","g")
| Running gdb:gdb.base/callfuncs.exp ...
| FAIL: gdb.base/callfuncs.exp: noproto: p t_char_array_values("carray 1","carray 2")
| ... and 125 more
Used configuration :
*CI config* tcwg_gnu_native_check_gdb 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-1934. (Require Linaro login) 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_native_check_gdb--master-aarch64-bu…
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_native_check_gdb--master-aarch64-bu…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_gdb--master-aarch64-bu…
Current build : http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_gdb--master-aarch64-bu…
Reference build : http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_gdb--master-aarch64-bu…
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=9ed3576e61f7a87eb83d…
Hi,
This test is incorrect.
I apologize for the false detection.
This issue involves the emergence of precision errors due to a change in the evaluation path for complex number division. Therefore, we will correct the tests.
It may take some time due to our internal release process, sorry.
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年6月15日 14:56
宛先: 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>; carlo.bertolli(a)amd.com <carlo.bertolli(a)amd.com>
件名: [Linaro-TCWG-CI] llvmorg-23-init-18988-g9ce63d09cff0: 2 regressions 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-18988-g9ce63d09cff0
| Author: carlobertolli <carlo.bertolli(a)amd.com>
| Date: Thu Jun 11 14:19:36 2026 -0500
|
| [AMDGPU][SCEV] Tighten max backedge-taken count for shift recurrence loops. (#197292)
|
| Application code on AMDGPUs often uses the following pattern:
|
| for (int i = blockDim.x / 2; i >= 1; i >>= 1)
| ... 19 lines of the commit log omitted.
Produces 2 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0640 ...
| FAIL: test-suite :: Fujitsu/Fortran/0640/Fujitsu-Fortran-0640_0306.test
| Running test-suite:Fujitsu/Fortran/0641 ...
| FAIL: test-suite :: Fujitsu/Fortran/0641/Fujitsu-Fortran-0641_0279.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-2234. (Require Linaro login) 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/9ce63d09cff0bf07da9623b75301011…
This seem like a testplatform issue, as this test (and many others) fails
with:
qemu-arm: unable to find CPU model 'cortex-a9'
On Mon, Jun 22, 2026 at 11:10 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-17-1246-g341ad729c2c
> | Author: Tomasz Kamiński <tkaminsk(a)redhat.com>
> | Date: Thu May 28 08:37:33 2026 +0200
> |
> | libstdc++: Add (generic_)display_string and
> (generic_)native_encoded_string to filesystem::path
> |
> | Furthermore string and generic_string method as marked as
> deprecated
> | in C++26 mode.
> |
> | ... 54 lines of the commit log omitted.
>
> Produces 2 regressions:
> |
> | regressions.sum:
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL: 27_io/filesystem/path/generic/display_native_string.cc
> -std=gnu++26 execution test
> | FAIL: 27_io/filesystem/path/native/display_native_string.cc
> -std=gnu++26 execution test
>
> 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-1938. (Require Linaro login)
> 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-arm_v7a_sof…
> 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-arm_v7a_sof…
> The list of [ignored] baseline and flaky failures are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_v7a_sof…
>
> Current build :
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_v7a_sof…
> Reference build :
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_v7a_sof…
>
> 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 reaching out regarding regression emails I received from your CI about the patch series I submitted recently.
V1 (submitted on 18.05.2026): https://patchwork.sourceware.org/project/gdb/cover/20260518183316.127043-1-…
V2 (submitted on 11.06.2026): https://patchwork.sourceware.org/project/gdb/cover/20260611153232.3011-1-mo…
The regressions were reported for the V2 series, in which no functional changes were introduced (only commit message updates). I am wondering if your CI has been passing for V1 or was not triggered?
I would appreciate your help in determining whether the reported regressions are legitimate or false positives. If they are indeed regressions introduced by my changes, I would greatly appreciate guidance on the reproduction steps.
Thanks,
--Mohamed
Intel Deutschland GmbH
Registered Address: Dornacher Strasse 1, 85622 Feldkirchen, Germany
Tel: +49 89 991 430, www.intel.de
Managing Directors: Harry Demas, Jeffrey Schneiderman, Yin Chong Sorrell
Chairperson of the Supervisory Board: Nicole Lau
Registered Seat: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
On Tue, Jun 16, 2026 at 3:30 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 aarch64 native, after:
> | commit gcc-17-1571-ga05a055bb2fb
> | Author: Andrew Pinski <andrew.pinski(a)oss.qualcomm.com>
> | Date: Fri Jun 12 11:40:35 2026 -0700
> |
> | phiopt: reorganize factoring/cselim-limited for phiopt
> |
> | This is in preparation for adding factoring out loads
> | for phiopt were we want to loop over all 3 factoring
> | cases if one of them made a change so that a load elimination
> | ... 15 lines of the commit log omitted.
>
> Produces 2 regressions:
> |
> | regressions.sum:
> | Running gcc:gcc.target/aarch64/aarch64.exp ...
> | FAIL: gcc.target/aarch64/fuse_cmp_csel-1.c check-function-bodies f1
> | FAIL: gcc.target/aarch64/fuse_cmp_csel-1.c check-function-bodies f2
The check here is too restrictive.
It is checking for gt but we now produce le. Both are valid.
cmp w0, w1
csel w3, w4, w3, le
add w0, w2, w3
I will make both fuse_cmp_csel.c and fuse_cmp_csel-1.c less restive
when it comes to the le/gt issue.
Thanks,
Andrea
>
> 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-1928. (Require Linaro login) 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
Hi,
There are two issues with this issue.
Regarding the first one, the testset was crashing during compilation, but the commit (ef4fb183a8d5c0d1910f7b5b6776ba669d6795ef) resolved the crash during compilation.
Regarding the second issue, the testset (0737_0019.f90) is incorrect.
It passes a function that returns a pointer array to an argument expecting a function that returns an allocatable array, and passes a function that returns an allocatable array to an argument expecting a function that returns a pointer array.
Since this is an incorrect testset, we'll correct it.
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 年 6 月 4 日 (木曜日) 6:25
宛先: 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>; 47756807+khaki3(a)users.noreply.github.com <47756807+khaki3(a)users.noreply.github.com>
件名: [Linaro-TCWG-CI] llvmorg-23-init-17574-g1872f06d60f3: 18 regressions 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-17574-g1872f06d60f3
| Author: khaki3 <47756807+khaki3(a)users.noreply.github.com>
| Date: Tue Jun 2 04:55:05 2026 -0700
|
| [flang][HLFIR] Add SeparateAllocatableAssign pass (#197814)
|
| Example:
| ```fortran
| !$\acc kernels
| ... 17 lines of the commit log omitted.
Produces 18 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0134 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0134/Fujitsu-Fortran-0134_0211.test
| Running test-suite:Fujitsu/Fortran/0299 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0299/Fujitsu-Fortran-0299_0038.test
| Running test-suite:Fujitsu/Fortran/0390 ...
| ... and 21 more
| # "NOEXE" means : the test program cannot be compiled
| # "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-2230. (Require Linaro login) 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/1872f06d60f35133bbc06e047c763b4…
Hi,
This test is incorrect. There is an error in how the volatile attribute of the variable k is handled when using setjmp and longjmp.
Therefore, we'll correct testset.
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年6月6日 14:23
宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com>
CC: npopov(a)redhat.com <npopov(a)redhat.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>
件名: [Linaro-TCWG-CI] llvmorg-23-init-17879-gf02dd4afbac1: 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-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays, after:
| commit llvmorg-23-init-17879-gf02dd4afbac1
| Author: Nikita Popov <npopov(a)redhat.com>
| Date: Thu Jun 4 09:26:12 2026 +0200
|
| [CaptureTracking] Volatile operations only capture address (#201316)
|
| The fact that a volatile access was performed on a certain address is an
| observable effect in the abstract machine, so volatile operations
| capture the address of the accessed pointer. However, they do not
| ... 6 lines of the commit log omitted.
Produces 1 regression:
|
| regressions.sum:
| Running test-suite:Fujitsu/C/0094 ...
| FAIL: test-suite :: Fujitsu/C/0094/Fujitsu-C-0094_0065.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 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG -fstack-arrays" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-2232. (Require Linaro login) 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-O3-neoverse_v1…
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-O3-neoverse_v1…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1…
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/f02dd4afbac15705016a9a7962d8716…
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 v11.0.0-1483-gc8bea1276c8
| Author: Philippe Mathieu-Daudé <philmd(a)linaro.org>
| Date: Fri May 15 12:40:14 2026 +0200
|
| target/arm: Build cpu32-system.o as common object
|
| cpu32.c only contains CPU types used in 32-bit system emulation:
| rename it as cpu32-system.c; always compile the file but only
| register the QOM types for the 32-bit binary.
| ... 6 lines of the commit log omitted.
Produces 38358 regressions 21 fixes:
|
| regressions.sum:
| Running g++:g++.dg/compat/compat.exp ...
| FAIL: g++.dg/compat/abi/bitfield1 cp_compat_x_tst.o-cp_compat_y_tst.o execute
| FAIL: g++.dg/compat/abi/bitfield2 cp_compat_x_tst.o-cp_compat_y_tst.o execute
| FAIL: g++.dg/compat/abi/pr83487-1 cp_compat_x_tst.o-cp_compat_y_tst.o execute
| FAIL: g++.dg/compat/abi/pr83487-2 cp_compat_x_tst.o-cp_compat_y_tst.o execute
| ... and 38390 more
|
| fixes.sum:
| Running g++:g++.dg/vect/vect.exp ...
| UNRESOLVED: g++.dg/vect/pr95401.cc -std=c++20 compilation failed to produce executable
| UNRESOLVED: g++.dg/vect/pr95401.cc -std=c++26 compilation failed to produce executable
| UNRESOLVED: g++.dg/vect/pr95401.cc -std=c++98 compilation failed to produce executable
| FAIL: g++.dg/vect/pr95401.cc -std=c++26 (test for excess errors)
| ... and 19 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-1925. (Require Linaro login) 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-arm_v7a_sof…
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-arm_v7a_sof…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_v7a_sof…
Current build : http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_v7a_sof…
Reference build : http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_v7a_sof…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/qemu/…
Full commit : https://gitlab.com/qemu-project/qemu/commit/c8bea1276c85855b2e088b740737d04…
Hi!
This seems to be an issue with your testing infrastructure. These
patches have not touched anything that isn't related to record-full so
there's no way they could be causing failures in gdb.arch tests. I guess
this test is no longer reliable.
--
Cheers,
Guinevere Larsen
It/she
On 6/7/26 3:44 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 gdb_check master-arm, after:
> | 3 patches in gdb
> | Patchwork URL: https://patchwork.sourceware.org/patch/136305
> | 1f3856ef4e9 [PATCH v4 3/8] gdb/record: remove record_full_insn_num
> | 9165d18a941 [PATCH v4 2/8] gdb/record: factor out reading and writing the execution log to corefile
> | 85ad6ec91da [PATCH v4 1/8] gdb/record: Refactor record history
> | ... applied on top of baseline commit:
> | 4562eab73d3 Automatic date update in version.in
>
> Produces 171 regressions:
> |
> | regressions.sum:
> | Running gdb:gdb.arch/skip-prologue.exp ...
> | FAIL: gdb.arch/skip-prologue.exp: f2: $\bp_addr == $\prologue_end_addr (skipped too much)
> | FAIL: gdb.arch/skip-prologue.exp: f4: $\bp_addr == $\prologue_end_addr (skipped too much)
> | Running gdb:gdb.arch/thumb2-it.exp ...
> | FAIL: gdb.arch/thumb2-it.exp: it_3, stepi 3
> | ... and 187 more
>
> Used configuration :
> *CI config* tcwg_gdb_check master-arm
> *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf
>
> 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_gdb_check--master-arm-precommit/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_gdb_check--master-arm-precommit/builds/…
> The list of [ignored] baseline and flaky failures are in
> * http://54.172.246.49:9090/jobs/tcwg_gdb_check--master-arm-precommit/builds/…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_gdb_check--master-arm-precommit/builds/…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_gdb_check--master-arm-build/builds/1021…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
Hi,
This test is incorrect.
I apologize for the false detection.
The criteria used in the test are inappropriate. Therefore, we will correct the test.
It may take some time due to our internal release process, sorry.
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 年 5 月 30 日 (土曜日) 13:36
宛先: 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-16289-g9c26d8c30c19: 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-16289-g9c26d8c30c19
| Author: Alexey Bataev <a.bataev(a)outlook.com>
| Date: Thu May 21 10:30:09 2026 -0400
|
| [SLP] Unify IR flag and metadata propagation in vectorizeTree
|
| Replace scattered propagateIRFlags/propagateMetadata calls with a single
| PropagateIRFlags lambda. Excludes copyable scalars from the flag
| intersection set and drops nnan/ninf when a copyable lane cannot prove
| ... 5 lines of the commit log omitted.
Produces 1 regression:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0118 ...
| FAIL: test-suite :: Fujitsu/Fortran/0118/Fujitsu-Fortran-0118_0266.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-2228. (Require Linaro login) 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/9c26d8c30c1971881d710cf62d0f50b…
Sorry for dropping the ball on this. I'm not really set up to do arm
glibc testing, so I'd initially hoped that this was the same as PR125599.
It turned out to be a different bug, PR125653, which should be fixed by
r17-1422-g4ab2c727829c53.
Thanks,
Richard
ci_notify(a)linaro.org writes:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please
> find some details below.
>
> In armv8l-unknown-linux-gnueabihf native, after:
> | commit gcc-17-1238-g8e3eff39a456
> | Author: Richard Sandiford <rdsandiford(a)googlemail.com>
> | Date: Tue Jun 2 20:50:27 2026 +0100
> |
> | backprop: Move opt-out for abnormal edges
> |
> | r6-6843-ga864ad5ba2501d made sure that optimize_phi wouldn't
> | optimise phi inputs for abnormal edges. See:
> |
> | ... 17 lines of the commit log omitted.
>
> Produces 147 regressions:
> |
> | regressions.sum:
> | Running glibc:stdio-common ...
> | FAIL: stdio-common/tst-printf
> | FAIL: stdio-common/tst-printf-format-as-c
> | FAIL: stdio-common/tst-printf-format-as-char
> | FAIL: stdio-common/tst-printf-format-as-int
> | ... and 143 more
>
> Used configuration :
> *CI config* tcwg_gnu_native_check_glibc armv8l-unknown-linux-gnueabihf
> *configure and test flags:* none, autodetected on
> armv8l-unknown-linux-gnueabihf--disable-multilib --with-float=hard
> --with-mode=thumb --with-tune=cortex-a9 --with-arch=armv7-a
> --with-fpu=neon-fp-armv8
>
> We track this bug report under
> https://linaro.atlassian.net/browse/GNU-1918. (Require Linaro login)
> 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_native_check_glibc--master-arm-buil…
> 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_native_check_glibc--master-arm-buil…
> The list of [ignored] baseline and flaky failures are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_glibc--master-arm-buil…
>
> Current build :
> http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_glibc--master-arm-buil…
> Reference build :
> http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_glibc--master-arm-buil…
>
> 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,
This test is incorrect.
I apologize for the false detection.
The criteria used in the test are inappropriate. Therefore, we will correct the test.
It may take some time due to our internal release process, sorry.
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 年 5 月 20 日 (水曜日) 20:15
宛先: 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>; jacob.crawley(a)arm.com <jacob.crawley(a)arm.com>
件名: [Linaro-TCWG-CI] llvmorg-23-init-15894-g304d077d4324: 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-15894-g304d077d4324
| Author: Jacob Crawley <jacob.crawley(a)arm.com>
| Date: Tue May 19 10:47:58 2026 +0100
|
| [AArch64] Add missing FSub case to isLegalToVectorizeReduction (#198302)
|
| Adds missing RecurKind::Fsub case to lower to partial reduction.
Produces 1 regression:
|
| regressions.sum:
| Running test-suite:Fujitsu/C/0022 ...
| FAIL: test-suite :: Fujitsu/C/0022/Fujitsu-C-0022_0039.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-2221. 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/304d077d43240d43408dc5595a00374…