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:
  | gcc patch https://patchwork.sourceware.org/patch/136004
  | Author: Nathan Myers <ncm@cantrip.org>
  | Date:   Thu May 28 18:09:46 2026 -0400
  | 
  |     [PATCH] libstdc++: guard with #if __cpp_aligned_new where needed
  |     
  |     __STDCPP_DEFAULT_NEW_ALIGNMENT__ is mentioned in several places
  |     not guarded with "#if __cpp_aligned_new". This patch fixes all
  |     except std/generator, the topic of PR125483.
  | ... 13 lines of the commit log omitted.
  | ... applied on top of baseline commit:
  | 8653813b1e4 aarch64: add __ARM_FEATURE_ macros for SVE2.2 and SME2.2

Produces Failure:
  | Results changed to
  | # reset_artifacts:
  | -10
  | # true:
  | 0
  | # build_abe bootstrap:
  | # FAILED
  | # First few build errors in logs:
  | # 00:10:58 /home/tcwg-build/workspace/tcwg_gnu_3/abe/snapshots/gcc.git~master/libstdc++-v3/src/c++17/fs_path.cc:255:19: error: ‘create_unchecked’ was not declared in this scope; did you mean ‘fread_unlocked’?
  | # 00:10:58 /home/tcwg-build/workspace/tcwg_gnu_3/abe/snapshots/gcc.git~master/libstdc++-v3/src/c++17/fs_path.cc:276:10: error: ‘_Impl’ does not name a type
  | # 00:10:58 /home/tcwg-build/workspace/tcwg_gnu_3/abe/snapshots/gcc.git~master/libstdc++-v3/src/c++17/fs_path.cc:283:10: error: ‘unique_ptr’ does not name a type
  | # 00:10:58 /home/tcwg-build/workspace/tcwg_gnu_3/abe/snapshots/gcc.git~master/libstdc++-v3/src/c++17/fs_path.cc:305:10: error: ‘unique_ptr’ does not name a type
  | # 00:10:58 /home/tcwg-build/workspace/tcwg_gnu_3/abe/snapshots/gcc.git~master/libstdc++-v3/src/c++17/fs_path.cc:319:37: error: ‘_Impl’ was not declared in this scope
  | # 00:10:58 /home/tcwg-build/workspace/tcwg_gnu_3/abe/snapshots/gcc.git~master/libstdc++-v3/src/c++17/fs_path.cc:319:57: error: ‘value_type’ was not declared in this scope
  | # 00:10:58 /home/tcwg-build/workspace/tcwg_gnu_3/abe/snapshots/gcc.git~master/libstdc++-v3/src/c++17/fs_path.cc:320:1: error: expected declaration before ‘}’ token
  | # 00:10:58 /home/tcwg-build/workspace/tcwg_gnu_3/abe/snapshots/gcc.git~master/libstdc++-v3/src/c++17/fs_path.cc:326:14: error: ‘notype’ is not a member of ‘std::filesystem::__cxx11::path::_List::_Impl’
  | # 00:10:58 /home/tcwg-build/workspace/tcwg_gnu_3/abe/snapshots/gcc.git~master/libstdc++-v3/src/c++17/fs_path.cc:329:33: error: ‘alloc_size’ is not a member of ‘std::filesystem::__cxx11::path::_List::_Impl’
  | # 00:10:58 /home/tcwg-build/workspace/tcwg_gnu_3/abe/snapshots/gcc.git~master/libstdc++-v3/src/c++17/fs_path.cc:355:26: error: ‘notype’ is not a member of ‘std::filesystem::__cxx11::path::_List::_Impl’
  | 
  | 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@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-bootstrap-precommit/builds/10150/archive/artifacts/artifacts.precommit/
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-bootstrap-precommit/builds/10150/archive/artifacts/artifacts.precommit/notify/

Current build   : http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-aarch64-bootstrap-precommit/builds/10150/archive/artifacts/
Reference build : http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-aarch64-bootstrap-build/builds/10074/archive/artifacts/

Warning: we do not enable maintainer-mode nor automatically update
generated files, which may lead to failures if the patch modifies the
master files.