On Thu, 19 Feb 2026 at 23:09, <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 gcc_check master-aarch64, after:
> | commit gcc-16-7593-g39edc2aea24f
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Tue Feb 17 12:48:51 2026 +0000
> |
> | libstdc++: Use global variables for default/max std in libstdc++.exp
> |
> | This simplifies the v3-minimum-std procedure slightly, but the main
> | advantage is making v3_modules_std depend on v3_max_std so that we don't
> | have to update two separate variables when new effective targets such as
> | ... 12 lines of the commit log omitted.
>
> Produces 4 regressions:
> |
> | regressions.sum:
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | ERROR: tcl error code TCL WRONGARGS
> | ERROR: tcl error sourcing libstdc++-dg/conformance.exp.
> | UNRESOLVED: testcase libstdc++-dg/conformance.exp' aborted due to Tcl error
> | ERROR: wrong # args: should be "v3-minimum-std test default_std max_std"
>
> Used configuration :
> *CI config* tcwg_gcc_check master-aarch64
> *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1842. Please let us know if you have a fix.
This should be fixed at r16-7599-g8d8725bedd2f7c
>
> 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_gcc_check--master-aarch64-build/4763/artifac…
> 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-build/4763/artifac…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/4763/artifac…
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/4763/artifac…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/4762/artifac…
>
> 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,
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!