Regressions on master at commit r16-54 vs commit r16-53 on Linux/x86_64

2025-04-21 Thread Haochen Jiang via Gcc-regression
Regressions on master at commit r16-54 vs commit r16-53 on Linux/x86_64
New failures:

New passes:
FAIL: gcc.target/i386/avx512fp16-trunc-extendvnhf.c scan-assembler-times 
vcvtpd2phx[ \\t]+[^{\n]*[^\n\r]*%xmm[0-9]+(?:\n|[ \\t]+#) 1
FAIL: gcc.target/i386/avx512fp16-trunc-extendvnhf.c scan-assembler-times 
vcvtpd2phx[ \\t]+[^{\n]*[^\n\r]*%xmm[0-9]+(?:\n|[ \\t]+#) 1


[Linaro-TCWG-CI] gcc-16-49-g49926c2c657: 9 regressions on arm

2025-04-21 Thread ci_notify--- via Gcc-regression
Dear contributor,

Our automatic CI has detected problems related to your patch(es). Please find 
some details below.

In gcc_check master-arm, after:
  | commit gcc-16-49-g49926c2c657
  | Author: Andrew Pinski 
  | Date:   Fri Mar 28 17:25:56 2025 -0700
  | 
  | except: Don't use the cached value of the gcc_except_table section for 
comdat functions [PR119507]
  | 
  | This has been broken since GCC started to put the comdat functions' 
gcc_except_table into their
  | own section; r0-118218-g3e6011cfebedfb. What would happen is after a 
non-comdat function is processed,
  | the cached value would always be used even for comdat function. Instead 
we should create a new
  | ... 16 lines of the commit log omitted.

Produces 9 regressions:
  | 
  | regressions.sum:
  | Running g++:g++.dg/dg.exp ...
  | FAIL: g++.dg/eh/pr119507.C -std=gnu++17  scan-assembler-times .section[\t 
][^\n]*.gcc_except_table 3
  | FAIL: g++.dg/eh/pr119507.C -std=gnu++17  scan-assembler-times .section[\t 
][^\n]*.gcc_except_table._Z6comdatv 1
  | FAIL: g++.dg/eh/pr119507.C -std=gnu++17  scan-assembler-times .section[\t 
][^\n]*.gcc_except_table._Z7comdat1v 1
  | FAIL: g++.dg/eh/pr119507.C -std=gnu++26  scan-assembler-times .section[\t 
][^\n]*.gcc_except_table 3
  | ... and 5 more

Used configuration :
 *CI config* tcwg_gcc_check master-arm
 *configure and test flags:* none, autodetected on 
armv8l-unknown-linux-gnueabihf

We track this bug report under https://linaro.atlassian.net/browse/GNU-1564. 
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 *.log.1.xz files in
 * 
https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3731/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/3731/artifact/artifacts/notify/
The list of [ignored] baseline and flaky failures are in
 * 
https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3731/artifact/artifacts/sumfiles/xfails.xfail

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

Instruction to reproduce the build : 
https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/49926c2c657dd867f7329df6e250913fd1425475/tcwg_gcc_check/master-arm/reproduction_instructions.txt

Full commit : 
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=49926c2c657dd867f7329df6e250913fd1425475