Dear contributor, Our automatic CI successfully passed with your patch(es). Please find some details below. In gcc_check master-aarch64, after: | gcc patch https://patchwork.sourceware.org/patch/131843 | Author: Jialong Wang | Date: Mon Mar 16 20:42:59 2026 -0400 | | [GSoC PATCH] libiberty: Add demangler recursion limit test | | Add a regression test for a deeply nested function type that exceeds the demangler recursion limit. The expected result is that demangling fails cleanly and leaves the mangled name unchanged, rather than crashing or overrunning recursion-sensitive paths. | | libiberty/ChangeLog: | ... 5 lines of the commit log omitted. | ... applied on top of baseline commit: | 60fbabc1a18 fortran: Preserve scalar class pointers in OpenMP privatization [PR120286] Used configuration : *CI config* tcwg_gcc_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@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-precommit/12179/artifact/artifacts/artifacts.precommit/00-sumfiles/ 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-precommit/12179/artifact/artifacts/artifacts.precommit/notify/ The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/12179/artifact/artifacts/artifacts.precommit/sumfiles/xfails.xfail Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/12179/artifact/artifacts Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/4874/artifact/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.