Dear contributor, Our automatic CI successfully passed with your patch(es). Please find some details below. In aarch64 native, after: | gcc patch https://patchwork.sourceware.org/patch/132442 | Author: Lulu Cheng | Date: Mon Mar 30 17:25:54 2026 +0800 | | [PATCH] LoongArch: Implement TARGET_CHECK_TARGET_CLONE_VERSION. | | This is to be able to ignore invalid versions to allow some portability | of code using target_clones attributes. | Add warning tests for invalid target_clones versions. | ... 21 lines of the commit log omitted. | ... applied on top of baseline commit: | bb91d2138e2 Daily bump. Used configuration : *CI config* tcwg_gcc_check aarch64-linux-gnu *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu--disable-multilib --enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a 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 * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/builds/10070/archive/artifacts/artifacts.precommit/00-sumfiles/ The full lists of regressions and improvements as well as configure and make commands are in * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/builds/10070/archive/artifacts/artifacts.precommit/notify/ The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/builds/10070/archive/artifacts/artifacts.precommit/sumfiles/xfails.xfail Current build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/builds/10070/archive/artifacts Reference build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/10025/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.