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
On Jan 31, 2026, ci_notify(a)linaro.org wrote:
> | regressions.sum:
> | Running gcc:gcc.target/arm/arm.exp ...
> | FAIL: gcc.target/arm/crypto-vsha1cq_u32.c scan-assembler-times
> | vdup.32\\tq[0-9]+, (?:r[0-9]+|d[0-9]+\\[[0-9]+\\]) 4
> |
> | fixes.sum:
> | Running gcc:gcc.target/arm/arm.exp ...
> | FAIL: gcc.target/arm/crypto-vsha1cq_u32.c scan-assembler-times
> | vdup.32\\tq[0-9]+, r[0-9]+ 4
That looks like still the same failure, but since the pattern is
textually different, it is no longer recognized as the same test point.
Unfortunately, the code this test run of yours generates doesn't match
the new pattern either. I guess the pattern will need to be extended
further.
--
Alexandre Oliva, happy hacker https://blog.lx.oliva.nom.br/
Free Software Activist FSFLA co-founder GNU Toolchain Engineer
More tolerance and less prejudice are key for inclusion and diversity.
Excluding neuro-others for not behaving ""normal"" is *not* inclusive!
Hi,
Thanks for the report. I have posted patch to fix the issue:
https://gcc.gnu.org/pipermail/gcc-patches/2026-January/707277.html
Can you please check if the above patch fixes the issue at your end ?
Thanks,
Prathamesh
> -----Original Message-----
> From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
> Sent: 23 January 2026 13:39
> To: Prathamesh Kulkarni <prathameshk(a)nvidia.com>
> Cc: gcc-regression(a)gcc.gnu.org; mmalcolmson(a)nvidia.com
> Subject: [Linaro-TCWG-CI] gcc-16-6913-g304d08fea9e6: 1 regression on
> arm
>
> External email: Use caution opening links or attachments
>
>
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es).
> Please find some details below.
>
> In master-arm, after:
> | commit gcc-16-6913-g304d08fea9e6
> | Author: Matthew Malcolmson <mmalcolmson(a)nvidia.com>
> | Date: Tue Jan 20 03:54:51 2026 +0000
> |
> | libgomp: Ensure memory sync after performing tasks
> |
> | As described in PR 122356 there is a theoretical bug around
> not
> | "publishing" user data written in a task when that task has
> been
> | executed by a thread after entry to a barrier.
> | ... 89 lines of the commit log omitted.
>
> Produces 1 regression:
> |
> | regressions.sum:
> | Running libgomp:libgomp.c/c.exp ...
> | FAIL: libgomp.c/pr122356.c execution test
>
> Used configuration :
> *CI config* tcwg_gnu_cross_check_gcc master-arm *configure and test
> flags:* --target arm-linux-gnueabihf
>
> We track this bug report under
> https://linaro.atlassian.net/browse/GNU-1822. Please let us know if
> you have a fix.
>
> If you have any questions regarding this report, please ask on linaro-
> toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<-----------------------
> ---8<--------------------------
>
> The information below contains the details of the failures, and the
> ways to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-
> build/2581/artifact/artifacts/00-sumfiles/
> The full lists of regressions and improvements as well as configure
> and make commands are in
> * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-
> build/2581/artifact/artifacts/notify/
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-
> build/2581/artifact/artifacts/sumfiles/xfails.xfail
>
> Current build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--
> master-arm-build/2581/artifact/artifacts
> Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--
> master-arm-build/2580/artifact/artifacts
>
> Instruction to reproduce the build :
> https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-
> /raw/master/gcc/sha1/304d08fea9e68c5b4806532816b58d33a15a917d/tcwg_gnu
> _cross_check_gcc/master-arm/reproduction_instructions.txt
>
> Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git
On Wed, Jan 21, 2026 at 5:50 AM <ci_notify(a)linaro.org> wrote:
>
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In arm-eabi cortex-m23 soft, after:
> | commit gcc-16-5975-gfae0c626250
> | Author: Andrew Pinski <andrew.pinski(a)oss.qualcomm.com>
> | Date: Sat Dec 6 01:11:29 2025 -0800
> |
> | final_cleanup: Call make_forwarders_with_degenerate_phis [PR46555]
> |
> | This fixes a regression introduced with r16-5258-g1d8e2d51e5c5cb.
> | With GCC 12+, we would not merge forwarders (with phis, vops included),
> | this meant that after the last cddce, degenerate phis would stay not
> | ... 22 lines of the commit log omitted.
>
> Produces 1 regression:
> |
> | regressions.sum:
> | Running gcc:gcc.dg/tree-ssa/tree-ssa.exp ...
> | FAIL: gcc.dg/tree-ssa/pr46555.c scan-rtl-dump pro_and_epilogue "Performing shrink-wrapping"
>
> Used configuration :
> *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv8-m.base -mtune=cortex-m23 -mfloat-abi=soft -mfpu=auto
> *configure and test flags:* --target arm-eabi --disable-multilib --with-mode=thumb --with-cpu=cortex-m23 --with-float=soft --target_board=-mthumb/-march=armv8-m.base/-mtune=cortex-m23/-mfloat-abi=soft/-mfpu=auto qemu_cpu=cortex-m33
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1819. Please let us know if you have a fix.
Filed https://gcc.gnu.org/bugzilla/show_bug.cgi?id=123751 and fixed in
r16-6969-g41878c161c480.
Thanks,
Andrew
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m23_soft_e…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m23_soft_e…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m23_soft_e…
>
> Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m23_soft_e…
> Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m23_soft_e…
>
> Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s…
>
> Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git
Hi,
This should be resolved by following commit that I have just pushed:
commit 5513935f48e50e97c854b746e758842c846a7740
Author: Tomasz Kamiński <tkaminsk(a)redhat.com>
Date: Wed Jan 7 17:24:55 2026 +0100
libstdc++: Use tree-dump-gimple in variant constant init tests.
Use of scan-assembler-dem for matching against debug symbols, turned
out to not
be portable, as they representation in assembly output differs between
platforms:
arm use 60 columns limit, emitting multiple rows, and some platforms
may encode
them using base64.
We use tree-dump-gimple instead, that outputs a constructor name
portably,
allowing us to simply match for invocation of constructor for given
type, as each
variable has different type.
To use scan-tree-dump(-not) we load scantree.exp file and it's
dependency
scandump.exp from gcc/testsuite/lib.
libstdc++-v3/ChangeLog:
* testsuite/20_util/variant/constinit.cc: Use scan-tree-dump
for matching of constructor.
* testsuite/20_util/variant/constinit_compat.cc: Likewise.
* testsuite/lib/libstdc++.exp: Load scantree.exp and
scandump.exp.
Regards,
Tomasz
On Thu, Dec 25, 2025 at 8:42 AM <ci_notify(a)linaro.org> wrote:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please
> find some details below.
>
> In master-arm, after:
> | commit gcc-16-6301-gb3c167b61fd7
> | Author: Tomasz Kamiński <tkaminsk(a)redhat.com>
> | Date: Thu Dec 11 10:43:44 2025 +0100
> |
> | libstdc++: Use union to store non-trivially destructible types in
> C++17 mode [PR112591]
> |
> | This patch disables use of specialization _Uninitialized<_Type,
> false> for
> | non-trivially destructible types by default in C++17, and
> fallbacks to
> | the primary template, that stores the type in union directly.
> This makes the
> | ... 39 lines of the commit log omitted.
>
> Produces 4 regressions:
> |
> | regressions.sum:
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL: 20_util/variant/constinit.cc -std=gnu++20 scan-assembler-dem
> (std::in_place_index_t<1ul?>, double&&)
> | FAIL: 20_util/variant/constinit.cc -std=gnu++20 scan-assembler-dem
> (std::in_place_index_t<1ul?>, int&&)
> | FAIL: 20_util/variant/constinit_compat.cc -std=gnu++20
> scan-assembler-dem (std::in_place_index_t<1ul?>, double&&)
> | FAIL: 20_util/variant/constinit_compat.cc -std=gnu++20
> scan-assembler-dem (std::in_place_index_t<1ul?>, int&&)
>
> Used configuration :
> *CI config* tcwg_gnu_cross_check_gcc master-arm
> *configure and test flags:* --target arm-linux-gnueabihf
>
> We track this bug report under
> https://linaro.atlassian.net/browse/GNU-1793. Please let us know if you
> have a fix.
>
> If you have any questions regarding this report, please ask on
> linaro-toolchain(a)lists.linaro.org mailing list.
>
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways
> to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> *
> https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/2498/a…
> The full lists of regressions and improvements as well as configure and
> make commands are in
> *
> https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/2498/a…
> The list of [ignored] baseline and flaky failures are in
> *
> https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/2498/a…
>
> Current build :
> https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/2498/a…
> Reference build :
> https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/2497/a…
>
> Instruction to reproduce the build :
> https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s…
>
> Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git