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
On Tue, Dec 30, 2025 at 11:36 PM <ci_notify(a)linaro.org> wrote:
>
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In arm-eabi v7-a softfp, after:
> | commit gcc-16-5947-ga6c50ec2c6e
> | Author: H.J. Lu <hjl.tools(a)gmail.com>
> | Date: Fri Oct 24 09:00:59 2025 +0800
> |
> | Add -ffuse-ops-with-volatile-access
> |
> | Volatile memory can be used as source operand for any operations. Add
> | -ffuse-ops-with-volatile-access to fuse operations with volatile memory
> | reference and update simplify_binary_operation_1 to keep PLUS for 2
> | ... 227 lines of the commit log omitted.
>
> Produces 6 regressions:
> |
> | regressions.sum:
> | Running gcc:gcc.target/arm/arm.exp ...
> | FAIL: gcc.target/arm/bfloat16_scalar_1_2.c check-function-bodies stacktest1
> | FAIL: gcc.target/arm/bfloat16_scalar_2_2.c check-function-bodies stacktest1
> | FAIL: gcc.target/arm/bfloat16_scalar_3_2.c check-function-bodies stacktest1
> | FAIL: gcc.target/arm/bfloat16_simd_1_2.c check-function-bodies stacktest1
Please check if the outputs are functional correct.
> | ... and 2 more
>
> Used configuration :
> *CI config* tcwg_gnu_embed_check_gcc arm-eabi -marm -march=armv7-a -mfpu=vfpv3-d16 -mfloat-abi=softfp
> *configure and test flags:* --target arm-eabi --disable-multilib --with-mode=arm --with-arch=armv7-a --with-fpu=vfpv3-d16 --with-float=softfp --target_board=-marm/-march=armv7-a/-mfpu=vfpv3-d16/-mfloat-abi=softfp qemu_cpu=cortex-a9
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1798. Please let us know if you have a fix.
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e…
>
> Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e…
> Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e…
>
> Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s…
>
> Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git
--
H.J.
On Fri, 19 Dec 2025 at 16:40, <ci_notify(a)linaro.org> wrote:
>
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In bootstrap_build master-arm-bootstrap_O3, after:
> | commit gcc-16-6185-g487bd3ba4f1f
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Wed Dec 10 14:26:17 2025 +0000
> |
> | libstdc++: Optimize compilation time for signed/unsigned integer traits
> |
> | Replace the O(n) definitions using __is_one_of with constant-time
> | checks that look for a static member in the __is_integral_helper class
> | template. That class template is already specialized for every signed
> | ... 20 lines of the commit log omitted.
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap_O3:
> | # FAILED
> | # First few build errors in logs:
> | # 00:49:05 /home/tcwg-buildslave/workspace/tcwg_gnu_3/abe/builds/armv8l-unknown-linux-gnueabihf/armv8l-unknown-linux-gnueabihf/gcc-gcc.git~master-stage2/prev-armv8l-unknown-linux-gnueabihf/libstdc++-v3/include/bits/stl_bvector.h:183:9: internal compiler error: Segmentation fault
> | # 00:49:05 make[3]: *** [Makefile:1216: text-art/ruler.o] Error 1
> | # 00:49:05 make[2]: *** [Makefile:5200: all-stage3-gcc] Error 2
> | # 00:49:05 make[1]: *** [Makefile:26599: stage3-bubble] Error 2
> | # 00:49:05 make: *** [Makefile:1127: all] Error 2
> |
> | From
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap_O3:
> | 1
>
> Used configuration :
> *CI config* tcwg_bootstrap_build master-arm-bootstrap_O3
> *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1783. Please let us know if you have a fix.
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
Very strange - I don't know why this would trigger a segfault in the compiler.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in
> * https://ci.linaro.org/job/tcwg_bootstrap_build--master-arm-bootstrap_O3-bui…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_bootstrap_build--master-arm-bootstrap_O3-bui…
>
> Current build : https://ci.linaro.org/job/tcwg_bootstrap_build--master-arm-bootstrap_O3-bui…
> Reference build : https://ci.linaro.org/job/tcwg_bootstrap_build--master-arm-bootstrap_O3-bui…
>
> Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s…
>
> Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git
On Mon, Dec 08, 2025 at 03:55:08AM +0000, ci_notify(a)linaro.org wrote:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In tcwg_kernel/llvm-master-arm-mainline-allyesconfig, after:
> | commit v6.18-rc6-688-gcd41d3420ef6
> | Author: Jaroslav Kysela <perex(a)perex.cz>
> | Date: Wed Nov 26 10:16:35 2025 +0100
> |
> | ASoC: nau8325: add missing build config
> |
> | This configuration was missing from the initial commit.
> |
> | Found by Jiri Benc <jbenc(a)redhat.com>
> | ... 6 lines of the commit log omitted.
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # build_abe binutils:
> | -9
> | # build_kernel_llvm:
> | -5
> | # build_abe qemu:
> | -2
> | # linux_n_obj:
> | 23374
> | # First few build errors in logs:
> | # 00:26:11 sound/soc/codecs/nau8325.c:430:13: error: variable 'n2_max' is uninitialized when used here [-Werror,-Wuninitialized]
> | # 00:26:11 sound/soc/codecs/nau8325.c:431:11: error: variable 'ratio_sel' is uninitialized when used here [-Werror,-Wuninitialized]
Should be hidden with
https://git.kernel.org/broonie/c/2c7e5e17c05f1d5e10e63e1baff2b362cd08dcd6
but I am still not convinced that is a correct fix (but I don't really
care to push further on it).
https://lore.kernel.org/20251203214958.GC3060476@ax162/
Cheers,
Nathan
On 12/6/25 11:52 AM, ci_notify(a)linaro.org wrote:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In arm-eabi v7-a softfp, after:
> | commit gcc-16-5581-g3ad2e2d707c3
> | Author: Jason Merrill <jason(a)redhat.com>
> | Date: Tue Nov 11 15:58:01 2025 +0530
> |
> | driver/c++: add --compile-std-module
> |
> | For simple testcases that want to use the std module, it would be useful to
> | have a reasonably short way to request building the binary module form
> | before the testcase. So with this patch users can write
> | ... 31 lines of the commit log omitted.
>
> Produces 1 regression:
> |
> | regressions.sum:
> | Running g++:g++.dg/modules/modules.exp ...
> | FAIL: g++.dg/modules/compile-std1.C -std=c++26 (test for excess errors)
It seems that module std doesn't compile on arm-eabi, which is good to know.
There seem to be two general issues: first, that some of the <stdio.h>
functions that <print> relies on aren't declared:
> /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-sta\
> ge2/arm-eabi/libstdc++-v3/include/print: In member function 'virtual void std::__format::_File_sink::_M_o\
> verflow()':
> /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-sta\
> ge2/arm-eabi/libstdc++-v3/include/print:197:20: error: '::fwrite_unlocked' has not been declared; did you\
> mean '_fwrite_unlocked_r'?
> /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-sta\
> ge2/arm-eabi/libstdc++-v3/include/print: In constructor 'std::__format::_File_sink::_File_sink(FILE*, boo\
> l)':
> /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-sta\
> ge2/arm-eabi/libstdc++-v3/include/print:212:9: error: '::flockfile' has not been declared; did you mean '\
> _flockfile'?
> /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-sta\
> ge2/arm-eabi/libstdc++-v3/include/print: In destructor 'std::__format::_File_sink::~_File_sink()':
> /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-sta\
> ge2/arm-eabi/libstdc++-v3/include/print:218:11: error: '::putc_unlocked' has not been declared; did you m\
> ean '_putc_unlocked_r'?
> /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-sta\
> ge2/arm-eabi/libstdc++-v3/include/print:219:9: error: '::funlockfile' has not been declared; did you mean\
> '_funlockfile'?
It seems that newlib doesn't declare these functions under -std=c++26,
only -std=gnu++26. I don't know what the right approach to this is.
and then a bunch of "not declared" exports, such as
> /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-sta\
> ge2/arm-eabi/libstdc++-v3/include/bits/std.cc:1002:14: error: 'condition_variable' has not been declared \
> in 'std'
This looks like just needing to add more #if to std.cc, as below. OK
for trunk?
Incidentally, is it expected that arm-eabi doesn't support gthread?
Jason
Hi,
unfortunately I do not have arm system at hand. I tried to build this commit
on QEMU (qemu-system-arm) running Debian (armhf architecture) and I cannot
reproduce any of the regressions.
I'd appreciate some information on how to build and run suitable armv8l
system on QEMU (or, if that's easier, on Odroid-N2) - I could not find much.
Thanks! Jan
On Sun, 2025-11-30 at 10:46 +0000, ci_notify(a)linaro.org wrote:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In gdb_check master-arm, after:
> | commit gdb-17-branchpoint-981-gcc1fc6af415
> | Author: Jan Vrany <jan.vrany(a)labware.com>
> | Date: Fri Nov 28 13:47:02 2025 +0000
> |
> | gdb: change blockvector::contains() to handle blockvectors with "holes"
> |
> | This commit slightly changes the logic in blockvector::contains()
> | to handle a case where the blockvector contains blocks with disjoint
> | regions (see the comment in blockvector::contains for details).
> | ... 18 lines of the commit log omitted.
>
> Produces 77 regressions:
> |
> | regressions.sum:
> | Running gdb:gdb.base/annota1.exp ...
> | FAIL: gdb.base/annota1.exp: send SIGUSR1 (timeout)
> | Running gdb:gdb.base/annota3.exp ...
> | FAIL: gdb.base/annota3.exp: send SIGUSR1 (pattern 8)
> | Running gdb:gdb.base/sigstep.exp ...
> | ... and 87 more
>
> Used configuration :
> *CI config* tcwg_gdb_check master-arm
> *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1767. Please let us know if you have a fix.
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> * https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/3149/artifact/ar…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/3149/artifact/ar…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/3149/artifact/ar…
>
> Current build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/3149/artifact/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/3148/artifact/ar…
>
> Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gdb/s…
>
> Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=cc1fc6af4150b…
Hi there, thanks for picking up on this change.
I see there’s 1 regression and 3 fixes, I just want to check are the fixes previous miscompiles?
Thanks,
Luke
> On 17 Nov 2025, at 09:03, ci_notify(a)linaro.org wrote:
>
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In tcwg_flang_test/main-aarch64-Ofast-sve_vls-lto-lld, after:
> | commit llvmorg-22-init-14324-g02c68b3ef754
> | Author: Luke Lau <luke(a)igalia.com>
> | Date: Wed Nov 12 19:14:53 2025 +0800
> |
> | [VPlan] Plumb scalable register size through narrowInterleaveGroups (#167505)
> |
> | On RISC-V narrowInterleaveGroups doesn't kick in because the wrong
> | VectorRegWidth is passed to isConsecutiveInterleaveGroup.
> |
> | ... 10 lines of the commit log omitted.
>
> Produces 1 regression 3 fixes:
> |
> | regressions.sum:
> | Running test-suite:Fujitsu/Fortran/0363 ...
> | FAIL: test-suite :: Fujitsu/Fortran/0363/Fujitsu-Fortran-0363_0283.test
> | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
> |
> | fixes.sum:
> | Running test-suite:Fujitsu/Fortran/0105 ...
> | FAIL: test-suite :: Fujitsu/Fortran/0105/Fujitsu-Fortran-0105_0091.test
> | ... and 2 more
> | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
>
> Used configuration :
> * Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld
> * Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH}
> cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite"
>
> We track this bug report under https://linaro.atlassian.net/browse/LLVM-2121. Please let us know if you have a fix.
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…
>
> Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
>
> Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…
> Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…
>
> Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/…
>
> Full commit : https://github.com/llvm/llvm-project/commit/02c68b3ef7544b875da4052dfb58205…
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In master-aarch64, after:
| commit glibc-2.42.9000-537-gcd748a63ab1
| Author: Joseph Myers <josmyers(a)redhat.com>
| Date: Thu Nov 20 19:30:27 2025 +0000
|
| Implement C23 const-preserving standard library macros
|
| C23 makes various standard library functions, that return a pointer
| into an input array, into macros that return a pointer to const when
| the relevant argument passed to the macro is a pointer to const. (The
| ... 35 lines of the commit log omitted.
Produces 5 regressions:
|
| regressions.sum:
| Running gcc:gcc.dg/analyzer/analyzer.exp ...
| FAIL: gcc.dg/analyzer/strchr-1.c (test for warnings, line 32)
| FAIL: gcc.dg/analyzer/strchr-1.c (test for warnings, line 39)
| FAIL: gcc.dg/analyzer/strchr-1.c (test for excess errors)
| FAIL: gcc.dg/analyzer/strchr-1.c event at line 33 (test for warnings, line 32)
| ... and 1 more
Used configuration :
*CI config* tcwg_gnu_native_check_gcc master-aarch64
*configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu
We track this bug report under https://linaro.atlassian.net/browse/GNU-1756. Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
* https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/2…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/2…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/2…
Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/2…
Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/2…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/glibc…
Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=cd748a63ab1a7ae84617…