Hi,
I believe these may be flaky since I checked with my 4 patches on cfarm185 machine with following configure command
configure --prefix=/home/avinashd/opt --enable-languages=c,c++ -- target=aarch64-unknown-linux-gnu --disable-multilib --enable-fix- cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a -- disable-bootstrap
on top of the commit a5da203dd95900ba8bab16432667989f3d018c76 : xtensa: Make use of CONST.S instruction
On Fri, 2026-08-28 at 22:17 +0000, ci_notify@linaro.org wrote:
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In aarch64 native, after: | 4 patches in gcc | Patchwork URL: https://patchwork.sourceware.org/patch/142333 | 25ff335aad8 [PATCH 4/4] rs6000: Add sha3 builtins and documentation [RFC02645] | f47d33c1b4e [PATCH 3/4] rs6000: Add __dmr2048 type (QDOmode) and map it to DMR pair register | 1eb45af654c [PATCH 2/4] genmodes: Use wider types for mode_unit_size array based on max size
The only change in middle-end that has happened is with this patch (2/4). And that is to generate the macro MODE_UNIT_SIZE_TYPE instead of unsigned char. This should not have caused the below mentioned regressions. All other patches are rs6000 backend related.
Please let me know if these regressions are always reproducible or if I have tested it incorrectly on the cfarm185 machine. I can have a look at what is happening.
Thanks, Avinash Jayakar
| 63b651a8d8f [PATCH 1/4] rs6000: Add sha2 and shapad builtins [RFC02645] | ... applied on top of baseline commit: | aaa0f6b1e87 match.pd: fold reductions of vector duplicates and repeats [PR127039]
Produces 2 regressions: | | regressions.sum: | Running gcc:gcc.misc-tests/gcov.exp ... | FAIL: gcc.misc-tests/gcov-39.c gcov: 0 failures in line counts, 0 in branch percentages, 0 in condition/decision, 1 in prime-paths, 0 in return percentages, 0 in intermediate format, 0 failed in filters | FAIL: gcc.misc-tests/gcov-39.c line 175: expected 1/8 covered paths, was 1/7
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/buil... 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/buil... The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/buil...
Current build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/buil... Reference build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/1...
Warning: we do not enable maintainer-mode nor automatically update generated files, which may lead to failures if the patch modifies the master files.