Dear contributor, Our automatic CI successfully passed with your patch(es). Please find some details below. In gcc_build master-arm, after: | gcc patch https://patchwork.sourceware.org/patch/131906 | Author: Jakub Jelinek | Date: Wed Mar 18 15:19:42 2026 +0100 | | [PATCH] c++, v2: Handle RAW_DATA_CST and RANGE_EXPR in build_vec_init [PR124531] | | On Tue, Mar 17, 2026 at 09:54:04AM +0100, Jakub Jelinek wrote: | > So I'm wondering if it wouldn't be safer to use: | > if (init | ... 24 lines of the commit log omitted. | ... applied on top of baseline commit: | ed1dcba392b Daily bump. Produces Success: | Results changed to | # reset_artifacts: | -10 | # true: | 0 | # build_abe gcc: | 1 | | From | # reset_artifacts: | -10 | # true: | 0 | # build_abe gcc: | 1 Used configuration : *CI config* tcwg_gcc_build master-arm *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf 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 * https://ci.linaro.org/job/tcwg_gcc_build--master-arm-precommit/21339/artifact/artifacts/artifacts.precommit/ The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_gcc_build--master-arm-precommit/21339/artifact/artifacts/artifacts.precommit/notify/ Current build : https://ci.linaro.org/job/tcwg_gcc_build--master-arm-precommit/21339/artifact/artifacts Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-arm-build/4583/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.