[Linaro-TCWG-CI] gcc-16-1550-g9244ea4bf556: Failure on aarch64
Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In master-aarch64, after: | commit gcc-16-1550-g9244ea4bf556 | Author: Andrew MacLeod | Date: Mon Jun 16 15:41:47 2025 -0400 | | Snap subrange boundries to bitmask constraints. | | Ensure all subrange endpoints conform to the bitmask. | | PR tree-optimization/120661 | ... 9 lines of the commit log omitted. Produces Failure: | Results changed to | # reset_artifacts: | -10 | # true: | 0 | # build_abe binutils: | 1 | # build_abe gcc: | 2 | # build_abe linux: | 4 | # build_abe glibc: | # FAILED | # build_abe gdb: | # First few build errors in logs: | # 00:02:30 fnmatch_loop.c:546:57: error: ‘idx’ may be used uninitialized [-Werror=maybe-uninitialized] | # 00:02:30 fnmatch_loop.c:758:41: error: ‘idx’ may be used uninitialized [-Werror=maybe-uninitialized] | # 00:02:31 fnmatch_loop.c:544:54: error: ‘wextra’ may be used uninitialized [-Werror=maybe-uninitialized] | # 00:02:31 fnmatch_loop.c:749:50: error: ‘wextra’ may be used uninitialized [-Werror=maybe-uninitialized] | # 00:02:32 make[2]: *** [../o-iterator.mk:9: /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/builds/aarch64-unknown-linux-gnu/aarch64-unknown-linux-gnu/glibc-glibc.git~master/posix/fnmatch.o] Error 1 | # 00:02:32 make[1]: *** [Makefile:484: posix/subdir_lib] Error 2 | # 00:02:32 make: *** [Makefile:20: all] Error 2 | | From | # reset_artifacts: | -10 | # true: | 0 | # build_abe binutils: | 1 | # build_abe gcc: | 2 | # build_abe linux: | 4 | # build_abe glibc: | 5 | # build_abe gdb: | 6 Used configuration : *CI config* tcwg_gnu_native_build 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-1608. Please let us know if you have a fix. If you have any questions regarding this report, please ask on linaro-toolch...@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_gnu_native_build--master-aarch64-build/1088/artifact/artifacts/ The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_gnu_native_build--master-aarch64-build/1088/artifact/artifacts/notify/ Current build : https://ci.linaro.org/job/tcwg_gnu_native_build--master-aarch64-build/1088/artifact/artifacts Reference build : https://ci.linaro.org/job/tcwg_gnu_native_build--master-aarch64-build/1087/artifact/artifacts Instruction to reproduce the build : https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/gcc/sha1/9244ea4bf556381d3f7fb66154dc8944ebeb005c/tcwg_gnu_native_build/master-aarch64/reproduction_instructions.txt Full commit : See in git+ssh://linar...@gcc.gnu.org/git/gcc.git
Regressions on native/master at commit r16-1566 vs commit r16-1560 on Linux/x86_64
Regressions on master at commit r16-1566 vs commit r16-1560 on Linux/x86_64 New failures: New passes: FAIL: g++.dg/coroutines/torture/func-params-07.C -O2 execution test FAIL: g++.dg/coroutines/torture/func-params-07.C -O2 execution test
Regressions on master at commit r16-1565 vs commit r16-1559 on Linux/x86_64
Regressions on master at commit r16-1565 vs commit r16-1559 on Linux/x86_64 New failures: FAIL: 30_threads/async/async.cc -std=gnu++17 execution test New passes: FAIL: g++.dg/coroutines/torture/func-params-07.C -O2 execution test FAIL: g++.dg/coroutines/torture/func-params-07.C -O2 execution test
Regressions on master at commit r16-1567 vs commit r16-1565 on Linux/x86_64
Regressions on master at commit r16-1567 vs commit r16-1565 on Linux/x86_64 New failures: New passes: FAIL: 30_threads/async/async.cc -std=gnu++17 execution test
Re: [Linaro-TCWG-CI] gcc-16-1550-g9244ea4bf556: Failure on aarch64
Could you file a glibc bug for this please? It needs some analysis to see if it's an FP or not. There's actually a suppression for -Os already there: if (elem < table_size) { /* Compare the byte sequence but only if this is not part of a range. */ /* The compiler might warn that idx may be used uninitialized, however it will be reached iff elem < table_size which means that it was properly set in the loop above. */ DIAG_PUSH_NEEDS_COMMENT; DIAG_IGNORE_Os_NEEDS_COMMENT (8, "-Wmaybe-uninitialized"); if (! is_range # if WIDE_CHAR_VERSION && __wmemcmp (n, &wextra[1], c1) == 0 # else && memcmp (n, &extra[idx + 1], c1) == 0 # endif ) { n += c1 - 1; goto matched; } DIAG_POP_NEEDS_COMMENT;