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
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