[Linaro-TCWG-CI] gcc-15-3095-gc9377734b798: FAIL: 8 regressions on arm

ci_notify@linaro.org ci_notify@linaro.org
Fri Aug 23 01:57:09 GMT 2024


Dear contributor, our automatic CI has detected problems related to your patch(es).  Please find some details below.  If you have any questions, please follow up on linaro-toolchain@lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.

We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.

We track this report status in https://linaro.atlassian.net/browse/GNU-1319 , please let us know if you are looking at the problem and/or when you have a fix.

In gcc_check master-arm after:

  | commit gcc-15-3095-gc9377734b798
  | Author: Jeff Law <jlaw@ventanamicro.com>
  | Date:   Thu Aug 22 12:48:49 2024 -0600
  | 
  |     [PR rtl-optimization/116420] Fix interesting block bitmap DF dataflow
  |     
  |     The DF framework provides us a way to run dataflow problems on sub-graphs.
  |     Naturally a bitmap of interesting blocks is passed into those routines.   At a
  |     confluence point, the DF framework will not mark a block for re-processing if
  |     it's not in that set of interesting blocks.
  |     
  | ... 22 lines of the commit log omitted.

FAIL: 8 regressions

regressions.sum:
		=== gcc tests ===

Running gcc:gcc.dg/torture/dg-torture.exp ...
FAIL: gcc.dg/torture/pr116420.c -O0  execution test
FAIL: gcc.dg/torture/pr116420.c -O1  execution test
FAIL: gcc.dg/torture/pr116420.c -O2  execution test
FAIL: gcc.dg/torture/pr116420.c -O2 -flto -fno-use-linker-plugin -flto-partition=none  execution test
FAIL: gcc.dg/torture/pr116420.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects  execution test
FAIL: gcc.dg/torture/pr116420.c -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions  execution test
FAIL: gcc.dg/torture/pr116420.c -O3 -g  execution test
... and 2 more entries

You can find the failure logs in *.log.1.xz files in
 - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2594/artifact/artifacts/00-sumfiles/
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-arm-build/2594/artifact/artifacts/notify/
The list of [ignored] baseline and flaky failures are in
 - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2594/artifact/artifacts/sumfiles/xfails.xfail

The configuration of this build is:
CI config tcwg_gcc_check master-arm

-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:

Current build   : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2594/artifact/artifacts
Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2593/artifact/artifacts

Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/c9377734b798d8d311dfd3a5618dc49407703b93/tcwg_gcc_check/master-arm/reproduction_instructions.txt

Full commit : https://github.com/gcc-mirror/gcc/commit/c9377734b798d8d311dfd3a5618dc49407703b93

List of configurations that regressed due to this commit :
* tcwg_gcc_check
** master-arm
*** FAIL: 8 regressions
*** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/c9377734b798d8d311dfd3a5618dc49407703b93/tcwg_gcc_check/master-arm/details.txt
*** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2594/artifact/artifacts


More information about the Gcc-regression mailing list