Regressions on master at commit r16-716 vs commit r16-715 on Linux/x86_64

2025-05-18 Thread Haochen Jiang via Gcc-regression
Regressions on master at commit r16-716 vs commit r16-715 on Linux/x86_64
New failures:
FAIL: 30_threads/async/async.cc  -std=gnu++17 execution test

New passes:


Regressions on master at commit r16-717 vs commit r16-716 on Linux/x86_64

2025-05-18 Thread Haochen Jiang via Gcc-regression
Regressions on master at commit r16-717 vs commit r16-716 on Linux/x86_64
New failures:

New passes:
FAIL: 30_threads/async/async.cc  -std=gnu++17 execution test


Regressions on native/master at commit r16-726 vs commit r16-718 on Linux/x86_64

2025-05-18 Thread Haochen Jiang via Gcc-regression
Regressions on master at commit r16-726 vs commit r16-718 on Linux/x86_64
New failures:

New passes:
FAIL: gcc.target/i386/funcspec-5.c (test for excess errors)
FAIL: gcc.target/i386/funcspec-6.c (test for excess errors)
FAIL: gcc.target/i386/part-vect-vec_cmpbf.c (test for excess errors)
FAIL: gcc.target/i386/pr111068.c (test for excess errors)
FAIL: gcc.target/i386/pr111068.c (test for excess errors)
FAIL: gcc.target/i386/pr117946.c (test for excess errors)
FAIL: gcc.target/i386/vnniint16-auto-vectorize-3.c (test for excess errors)
FAIL: gcc.target/i386/vnniint16-auto-vectorize-3.c (test for excess errors)
FAIL: gcc.target/i386/vnniint8-auto-vectorize-3.c (test for excess errors)
FAIL: gcc.target/i386/vnniint8-auto-vectorize-3.c (test for excess errors)


[r16-645 Regression] FAIL: gcc.target/i386/vect-epilogues-5.c scan-tree-dump-times vect "loop vectorized using 64 byte vectors" 2 on Linux/x86_64

2025-05-18 Thread haochen.jiang via Gcc-regression
On Linux/x86_64,

af7b84d0d02ffa23e4843e9555a888c9e80bd9b5 is the first bad commit
commit af7b84d0d02ffa23e4843e9555a888c9e80bd9b5
Author: Richard Biener 
Date:   Wed May 14 16:45:08 2025 +0200

Enhance -fopt-info-vec vectorized loop diagnostic

caused

FAIL: gcc.target/i386/vect-epilogues-4.c scan-tree-dump-times vect "loop 
vectorized using 64 byte vectors" 2
FAIL: gcc.target/i386/vect-epilogues-5.c scan-tree-dump-times vect "loop 
vectorized using 64 byte vectors" 2

with GCC configured with

../../gcc/configure 
--prefix=/export/users/haochenj/src/gcc-bisect/master/master/r16-645/usr 
--enable-clocale=gnu --with-system-zlib --with-demangler-in-ld 
--with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet --without-isl 
--enable-libmpx x86_64-linux --disable-bootstrap

To reproduce:

$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="i386.exp=gcc.target/i386/vect-epilogues-4.c 
--target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="i386.exp=gcc.target/i386/vect-epilogues-4.c 
--target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="i386.exp=gcc.target/i386/vect-epilogues-4.c 
--target_board='unix{-m64}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="i386.exp=gcc.target/i386/vect-epilogues-4.c 
--target_board='unix{-m64\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="i386.exp=gcc.target/i386/vect-epilogues-5.c 
--target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="i386.exp=gcc.target/i386/vect-epilogues-5.c 
--target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="i386.exp=gcc.target/i386/vect-epilogues-5.c 
--target_board='unix{-m64}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="i386.exp=gcc.target/i386/vect-epilogues-5.c 
--target_board='unix{-m64\ -march=cascadelake}'"

(Please do not reply to this email, for question about this report, contact me 
at haochen dot jiang at intel.com.)
(If you met problems with cascadelake related, disabling AVX512F in command 
line might save that.)
(However, please make sure that there is no potential problems with AVX512.)


[r16-531 Regression] FAIL: gcc.target/i386/vect-shiftv8qi.c scan-assembler-times psllw 2 on Linux/x86_64

2025-05-18 Thread haochen.jiang via Gcc-regression
On Linux/x86_64,

37e61c793c1b22bdcfbf142cd6086da2745be596 is the first bad commit
commit 37e61c793c1b22bdcfbf142cd6086da2745be596
Author: Jan Hubicka 
Date:   Sun May 11 23:49:11 2025 +0200

i386: Fix move costs in vectorizer cost model.

caused

FAIL: gcc.target/i386/pr108938-3.c scan-assembler-times bswap[\t ]+ 3
FAIL: gcc.target/i386/pr111023-2.c scan-assembler (?:pcmpgtd|psrad)
FAIL: gcc.target/i386/pr111023-2.c scan-assembler (?:pcmpgtw|psraw)
FAIL: gcc.target/i386/pr111023-2.c scan-assembler punpckldq
FAIL: gcc.target/i386/pr111023-2.c scan-assembler punpcklwd
FAIL: gcc.target/i386/pr111023.c scan-assembler punpckldq
FAIL: gcc.target/i386/pr111023.c scan-assembler punpcklwd
FAIL: gcc.target/i386/vect-shiftv4qi.c scan-assembler-times psllw 2
FAIL: gcc.target/i386/vect-shiftv4qi.c scan-assembler-times psrlw 5
FAIL: gcc.target/i386/vect-shiftv8qi.c scan-assembler-times psllw 2
FAIL: gcc.target/i386/vect-shiftv8qi.c scan-assembler-times psrlw 5

with GCC configured with

../../gcc/configure 
--prefix=/export/users/haochenj/src/gcc-bisect/master/master/r16-531/usr 
--enable-clocale=gnu --with-system-zlib --with-demangler-in-ld 
--with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet --without-isl 
--enable-libmpx x86_64-linux --disable-bootstrap

To reproduce:

$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="i386.exp=gcc.target/i386/pr108938-3.c --target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="i386.exp=gcc.target/i386/pr108938-3.c --target_board='unix{-m32\ 
-march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="i386.exp=gcc.target/i386/pr111023-2.c --target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="i386.exp=gcc.target/i386/pr111023-2.c --target_board='unix{-m32\ 
-march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="i386.exp=gcc.target/i386/pr111023.c --target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="i386.exp=gcc.target/i386/pr111023.c --target_board='unix{-m32\ 
-march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="i386.exp=gcc.target/i386/vect-shiftv4qi.c 
--target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="i386.exp=gcc.target/i386/vect-shiftv4qi.c 
--target_board='unix{-m64\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="i386.exp=gcc.target/i386/vect-shiftv8qi.c 
--target_board='unix{-m64\ -march=cascadelake}'"

(Please do not reply to this email, for question about this report, contact me 
at haochen dot jiang at intel.com.)
(If you met problems with cascadelake related, disabling AVX512F in command 
line might save that.)
(However, please make sure that there is no potential problems with AVX512.)


[r16-372 Regression] FAIL: gfortran.dg/specifics_1.f90 -O3 -g execution test on Linux/x86_64

2025-05-18 Thread haochen.jiang via Gcc-regression
On Linux/x86_64,

064cac730f88dc71c6da578f9ae5b8e092ab6cd4 is the first bad commit
commit 064cac730f88dc71c6da578f9ae5b8e092ab6cd4
Author: Jan Hubicka 
Date:   Sun May 4 10:52:35 2025 +0200

Improve maybe_hot handling in inliner heuristics

caused

FAIL: gcc.dg/tree-ssa/gen-vect-28.c scan-tree-dump-times vect "Alignment of 
access forced using peeling" 1
FAIL: gcc.dg/tree-ssa/gen-vect-28.c scan-tree-dump-times vect "vectorized 1 
loops" 1
FAIL: gcc.dg/tree-ssa/pr81627.c scan-tree-dump-times pcom "Store-stores chain" 1
FAIL: gcc.target/i386/avx512vl-vpmovuswb-2.c (test for excess errors)
FAIL: gcc.target/i386/avx512vl-vpmovwb-2.c (test for excess errors)
FAIL: g++.dg/coroutines/torture/exceptions-test-01-n4849-a.C   -O2  execution 
test
FAIL: g++.dg/coroutines/torture/exceptions-test-01-n4849-a.C   -O2 -flto 
-fno-use-linker-plugin -flto-partition=none  execution test
FAIL: g++.dg/coroutines/torture/exceptions-test-01-n4849-a.C   -O3 -g  
execution test
FAIL: g++.dg/coroutines/torture/func-params-07.C   -O2  execution test
FAIL: g++.dg/coroutines/torture/func-params-07.C   -O3 -g  execution test
FAIL: g++.dg/coroutines/torture/pr103953.C   -O2  execution test
FAIL: g++.dg/coroutines/torture/pr103953.C   -O3 -g  execution test
FAIL: g++.dg/vect/pr64410.cc  -std=c++17  scan-tree-dump vect "vectorized 1 
loops in function"
FAIL: g++.dg/vect/pr64410.cc  -std=c++26  scan-tree-dump vect "vectorized 1 
loops in function"
FAIL: gfortran.dg/guality/arg1.f90   -O3 -fomit-frame-pointer -funroll-loops 
-fpeel-loops -ftracer -finline-functions  line 14 a(10) == 10
FAIL: gfortran.dg/specifics_1.f90   -O2  execution test
FAIL: gfortran.dg/specifics_1.f90   -O3 -fomit-frame-pointer -funroll-loops 
-fpeel-loops -ftracer -finline-functions  execution test
FAIL: gfortran.dg/specifics_1.f90   -O3 -g  execution test

with GCC configured with

../../gcc/configure 
--prefix=/export/users/haochenj/src/gcc-bisect/master/master/r16-372/usr 
--enable-clocale=gnu --with-system-zlib --with-demangler-in-ld 
--with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet --without-isl 
--enable-libmpx x86_64-linux --disable-bootstrap

To reproduce:

$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="tree-ssa.exp=gcc.dg/tree-ssa/gen-vect-28.c 
--target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="tree-ssa.exp=gcc.dg/tree-ssa/gen-vect-28.c 
--target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="tree-ssa.exp=gcc.dg/tree-ssa/pr81627.c 
--target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="tree-ssa.exp=gcc.dg/tree-ssa/pr81627.c --target_board='unix{-m32\ 
-march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="tree-ssa.exp=gcc.dg/tree-ssa/pr81627.c 
--target_board='unix{-m64}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="tree-ssa.exp=gcc.dg/tree-ssa/pr81627.c --target_board='unix{-m64\ 
-march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="i386.exp=gcc.target/i386/avx512vl-vpmovuswb-2.c 
--target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="i386.exp=gcc.target/i386/avx512vl-vpmovuswb-2.c 
--target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="i386.exp=gcc.target/i386/avx512vl-vpmovuswb-2.c 
--target_board='unix{-m64}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="i386.exp=gcc.target/i386/avx512vl-vpmovuswb-2.c 
--target_board='unix{-m64\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="i386.exp=gcc.target/i386/avx512vl-vpmovwb-2.c 
--target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="i386.exp=gcc.target/i386/avx512vl-vpmovwb-2.c 
--target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="i386.exp=gcc.target/i386/avx512vl-vpmovwb-2.c 
--target_board='unix{-m64}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="i386.exp=gcc.target/i386/avx512vl-vpmovwb-2.c 
--target_board='unix{-m64\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="coro-torture.exp=g++.dg/coroutines/torture/exceptions-test-01-n4849-a.C
 --target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="coro-torture.exp=g++.dg/coroutines/torture/exceptions-test-01-n4849-a.C
 --target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="coro-torture.exp=g++.dg/coroutines/torture/exceptions-test-01-n4849-a.C
 --target_board='unix{-m64}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="coro-torture.exp=g++.dg/coroutines/torture/exceptions-test-01-n4849-a.C
 --target_board='unix{-m64\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="coro-torture.exp=g++.dg/coroutines/torture/func-params-07.C 
--target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="coro-torture.exp=g++.dg/coroutines/torture/func-params-07.C 
--target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_d

[r16-385 Regression] FAIL: gcc.dg/vect/vect-simd-clone-18d.c scan-tree-dump-times vect "[\\n\\r] [^\\n]* = foo\\.simdclone" 2 on Linux/x86_64

2025-05-18 Thread haochen.jiang via Gcc-regression
On Linux/x86_64,

c9982eec2d3edc5306291d4628f08825ba46d483 is the first bad commit
commit c9982eec2d3edc5306291d4628f08825ba46d483
Author: Thomas Schwinge 
Date:   Mon May 5 10:21:35 2025 +0200

vect-simd-clone-1[6-8][cd].c: Expect in-branch clones for x86: Fix target 
selector syntax

caused

FAIL: gcc.dg/vect/vect-simd-clone-16c.c scan-tree-dump-times vect "[\\n\\r] 
[^\\n]* = foo\\.simdclone" 2
FAIL: gcc.dg/vect/vect-simd-clone-16d.c scan-tree-dump-times vect "[\\n\\r] 
[^\\n]* = foo\\.simdclone" 2
FAIL: gcc.dg/vect/vect-simd-clone-17c.c scan-tree-dump-times vect "[\\n\\r] 
[^\\n]* = foo\\.simdclone" 2
FAIL: gcc.dg/vect/vect-simd-clone-17d.c scan-tree-dump-times vect "[\\n\\r] 
[^\\n]* = foo\\.simdclone" 2
FAIL: gcc.dg/vect/vect-simd-clone-18c.c scan-tree-dump-times vect "[\\n\\r] 
[^\\n]* = foo\\.simdclone" 2
FAIL: gcc.dg/vect/vect-simd-clone-18d.c scan-tree-dump-times vect "[\\n\\r] 
[^\\n]* = foo\\.simdclone" 2

with GCC configured with

../../gcc/configure 
--prefix=/export/users/haochenj/src/gcc-bisect/master/master/r16-385/usr 
--enable-clocale=gnu --with-system-zlib --with-demangler-in-ld 
--with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet --without-isl 
--enable-libmpx x86_64-linux --disable-bootstrap

To reproduce:

$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="vect.exp=gcc.dg/vect/vect-simd-clone-16c.c 
--target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="vect.exp=gcc.dg/vect/vect-simd-clone-16c.c 
--target_board='unix{-m64\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="vect.exp=gcc.dg/vect/vect-simd-clone-16d.c 
--target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="vect.exp=gcc.dg/vect/vect-simd-clone-16d.c 
--target_board='unix{-m64\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="vect.exp=gcc.dg/vect/vect-simd-clone-17c.c 
--target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="vect.exp=gcc.dg/vect/vect-simd-clone-17c.c 
--target_board='unix{-m64\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="vect.exp=gcc.dg/vect/vect-simd-clone-17d.c 
--target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="vect.exp=gcc.dg/vect/vect-simd-clone-17d.c 
--target_board='unix{-m64\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="vect.exp=gcc.dg/vect/vect-simd-clone-18c.c 
--target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="vect.exp=gcc.dg/vect/vect-simd-clone-18c.c 
--target_board='unix{-m64\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="vect.exp=gcc.dg/vect/vect-simd-clone-18d.c 
--target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="vect.exp=gcc.dg/vect/vect-simd-clone-18d.c 
--target_board='unix{-m64\ -march=cascadelake}'"

(Please do not reply to this email, for question about this report, contact me 
at haochen dot jiang at intel.com.)
(If you met problems with cascadelake related, disabling AVX512F in command 
line might save that.)
(However, please make sure that there is no potential problems with AVX512.)


RE: x86 Bisect script is currently down

2025-05-18 Thread Jiang, Haochen via Gcc-regression
The script is back online for now. But still with some issues
on automation due to the machine config after crash.

I will run the script on at least a daily basis for a temporary
solution.

Thx,
Haochen

From: Jiang, Haochen
Sent: Wednesday, May 14, 2025 10:51 AM
To: gcc-regression@gcc.gnu.org
Subject: x86 Bisect script is currently down

Hi all,

During my vacation last three weeks, it seems to me that
my bisect script is down. After I am back from my holiday
this week, I found that the machine OS disk is totally down.

Please expect some time to bring that bisect script back. The
Test regression reporter is still running. (However, with quite
a few false positive for a long time due to timeout issue and
hard to fix unless I found other powerful machines.)

Thx,
Haochen


[r16-517 Regression] FAIL: gcc.target/i386/pr78794.c scan-assembler pandn on Linux/x86_64

2025-05-18 Thread haochen.jiang via Gcc-regression
On Linux/x86_64,

993aa0bd28722c7f01fb8310f1c79814aef217ed is the first bad commit
commit 993aa0bd28722c7f01fb8310f1c79814aef217ed
Author: Jan Hubicka 
Date:   Sat May 10 22:23:48 2025 +0200

i386: Fix some problems in stv cost model

caused

FAIL: gcc.target/i386/avx512vl-stv-rotatedi-1.c scan-assembler-times vpro[lr]q 
29
FAIL: gcc.target/i386/pr78794.c scan-assembler pandn

with GCC configured with

../../gcc/configure 
--prefix=/export/users/haochenj/src/gcc-bisect/master/master/r16-517/usr 
--enable-clocale=gnu --with-system-zlib --with-demangler-in-ld 
--with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet --without-isl 
--enable-libmpx x86_64-linux --disable-bootstrap

To reproduce:

$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="i386.exp=gcc.target/i386/avx512vl-stv-rotatedi-1.c 
--target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="i386.exp=gcc.target/i386/pr78794.c --target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check 
RUNTESTFLAGS="i386.exp=gcc.target/i386/pr78794.c --target_board='unix{-m32\ 
-march=cascadelake}'"

(Please do not reply to this email, for question about this report, contact me 
at haochen dot jiang at intel.com.)
(If you met problems with cascadelake related, disabling AVX512F in command 
line might save that.)
(However, please make sure that there is no potential problems with AVX512.)


[r16-334 Regression] FAIL: gcc.dg/Wincompatible-pointer-types-1.c (test for excess errors) on Linux/x86_64

2025-05-18 Thread haochen.jiang via Gcc-regression
On Linux/x86_64,

b6d37ec1dd2a228d94e7b5b438f3aa53684316bc is the first bad commit
commit b6d37ec1dd2a228d94e7b5b438f3aa53684316bc
Author: Florian Weimer 
Date:   Thu May 1 19:06:45 2025 +0200

c: Suppress -Wdeprecated-non-prototype warnings for builtins

caused

FAIL: gcc.c-torture/compile/callind.c   -O0  (internal compiler error: 
Segmentation fault)
FAIL: gcc.c-torture/compile/callind.c   -O0  (test for excess errors)
FAIL: gcc.c-torture/compile/callind.c   -O1  (internal compiler error: 
Segmentation fault)
FAIL: gcc.c-torture/compile/callind.c   -O1  (test for excess errors)
FAIL: gcc.c-torture/compile/callind.c   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  (internal compiler error: Segmentation fault)
FAIL: gcc.c-torture/compile/callind.c   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  (test for excess errors)
FAIL: gcc.c-torture/compile/callind.c   -O2 -flto -fuse-linker-plugin 
-fno-fat-lto-objects  (internal compiler error: Segmentation fault)
FAIL: gcc.c-torture/compile/callind.c   -O2 -flto -fuse-linker-plugin 
-fno-fat-lto-objects  (test for excess errors)
FAIL: gcc.c-torture/compile/callind.c   -O2  (internal compiler error: 
Segmentation fault)
FAIL: gcc.c-torture/compile/callind.c   -O2  (test for excess errors)
FAIL: gcc.c-torture/compile/callind.c   -O3 -g  (internal compiler error: 
Segmentation fault)
FAIL: gcc.c-torture/compile/callind.c   -O3 -g  (test for excess errors)
FAIL: gcc.c-torture/compile/callind.c   -Os  (internal compiler error: 
Segmentation fault)
FAIL: gcc.c-torture/compile/callind.c   -Os  (test for excess errors)
FAIL: gcc.c-torture/compile/pr51694.c   -O0  (internal compiler error: 
Segmentation fault)
FAIL: gcc.c-torture/compile/pr51694.c   -O0  (test for excess errors)
FAIL: gcc.c-torture/compile/pr51694.c   -O1  (internal compiler error: 
Segmentation fault)
FAIL: gcc.c-torture/compile/pr51694.c   -O1  (test for excess errors)
FAIL: gcc.c-torture/compile/pr51694.c   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  (internal compiler error: Segmentation fault)
FAIL: gcc.c-torture/compile/pr51694.c   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  (test for excess errors)
FAIL: gcc.c-torture/compile/pr51694.c   -O2 -flto -fuse-linker-plugin 
-fno-fat-lto-objects  (internal compiler error: Segmentation fault)
FAIL: gcc.c-torture/compile/pr51694.c   -O2 -flto -fuse-linker-plugin 
-fno-fat-lto-objects  (test for excess errors)
FAIL: gcc.c-torture/compile/pr51694.c   -O2  (internal compiler error: 
Segmentation fault)
FAIL: gcc.c-torture/compile/pr51694.c   -O2  (test for excess errors)
FAIL: gcc.c-torture/compile/pr51694.c   -O3 -g  (internal compiler error: 
Segmentation fault)
FAIL: gcc.c-torture/compile/pr51694.c   -O3 -g  (test for excess errors)
FAIL: gcc.c-torture/compile/pr51694.c   -Os  (internal compiler error: 
Segmentation fault)
FAIL: gcc.c-torture/compile/pr51694.c   -Os  (test for excess errors)
FAIL: gcc.c-torture/execute/pr67037.c   -O0  (internal compiler error: 
Segmentation fault)
FAIL: gcc.c-torture/execute/pr67037.c   -O0  (test for excess errors)
FAIL: gcc.c-torture/execute/pr67037.c   -O1  (internal compiler error: 
Segmentation fault)
FAIL: gcc.c-torture/execute/pr67037.c   -O1  (test for excess errors)
FAIL: gcc.c-torture/execute/pr67037.c   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  (internal compiler error: Segmentation fault)
FAIL: gcc.c-torture/execute/pr67037.c   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  (test for excess errors)
FAIL: gcc.c-torture/execute/pr67037.c   -O2 -flto -fuse-linker-plugin 
-fno-fat-lto-objects  (internal compiler error: Segmentation fault)
FAIL: gcc.c-torture/execute/pr67037.c   -O2 -flto -fuse-linker-plugin 
-fno-fat-lto-objects  (test for excess errors)
FAIL: gcc.c-torture/execute/pr67037.c   -O2  (internal compiler error: 
Segmentation fault)
FAIL: gcc.c-torture/execute/pr67037.c   -O2  (test for excess errors)
FAIL: gcc.c-torture/execute/pr67037.c   -O3 -fomit-frame-pointer -funroll-loops 
-fpeel-loops -ftracer -finline-functions  (internal compiler error: 
Segmentation fault)
FAIL: gcc.c-torture/execute/pr67037.c   -O3 -fomit-frame-pointer -funroll-loops 
-fpeel-loops -ftracer -finline-functions  (test for excess errors)
FAIL: gcc.c-torture/execute/pr67037.c   -O3 -g  (internal compiler error: 
Segmentation fault)
FAIL: gcc.c-torture/execute/pr67037.c   -O3 -g  (test for excess errors)
FAIL: gcc.c-torture/execute/pr67037.c   -Os  (internal compiler error: 
Segmentation fault)
FAIL: gcc.c-torture/execute/pr67037.c   -Os  (test for excess errors)
FAIL: gcc.dg/analyzer/torture/pr93379.c   -O0  (internal compiler error: 
Segmentation fault)
FAIL: gcc.dg/analyzer/torture/pr93379.c   -O0  (test for excess errors)
FAIL: gcc.dg/analyzer/torture/pr93379.c   -O1  (internal compiler error: 
Segmentation fault)
FAIL: gcc.dg/analyzer/torture/pr93379.c   -O1  (test for excess errors)
FAIL: gcc.dg/analyzer/torture/pr93379.c   -O2 -flto -fno-use-linker-plugi

Re: [r16-372 Regression] FAIL: gfortran.dg/specifics_1.f90 -O3 -g execution test on Linux/x86_64

2025-05-18 Thread Andrew Pinski via Gcc-regression
On Sun, May 18, 2025 at 11:19 PM haochen.jiang
 wrote:
>
> On Linux/x86_64,
>
> 064cac730f88dc71c6da578f9ae5b8e092ab6cd4 is the first bad commit
> commit 064cac730f88dc71c6da578f9ae5b8e092ab6cd4
> Author: Jan Hubicka 
> Date:   Sun May 4 10:52:35 2025 +0200
>
> Improve maybe_hot handling in inliner heuristics
>
> caused
>
> FAIL: gcc.dg/tree-ssa/gen-vect-28.c scan-tree-dump-times vect "Alignment of 
> access forced using peeling" 1
> FAIL: gcc.dg/tree-ssa/gen-vect-28.c scan-tree-dump-times vect "vectorized 1 
> loops" 1
> FAIL: gcc.dg/tree-ssa/pr81627.c scan-tree-dump-times pcom "Store-stores 
> chain" 1

This is just an extra inlining which causes pcom to happen twice now.
Will look into fix that this coming week.


> FAIL: gcc.target/i386/avx512vl-vpmovuswb-2.c (test for excess errors)
> FAIL: gcc.target/i386/avx512vl-vpmovwb-2.c (test for excess errors)
> FAIL: g++.dg/coroutines/torture/exceptions-test-01-n4849-a.C   -O2  execution 
> test
> FAIL: g++.dg/coroutines/torture/exceptions-test-01-n4849-a.C   -O2 -flto 
> -fno-use-linker-plugin -flto-partition=none  execution test
> FAIL: g++.dg/coroutines/torture/exceptions-test-01-n4849-a.C   -O3 -g  
> execution test
> FAIL: g++.dg/coroutines/torture/func-params-07.C   -O2  execution test
> FAIL: g++.dg/coroutines/torture/func-params-07.C   -O3 -g  execution test
> FAIL: g++.dg/coroutines/torture/pr103953.C   -O2  execution test
> FAIL: g++.dg/coroutines/torture/pr103953.C   -O3 -g  execution test

The coroutines failures might be a front-end issue or a testcase issue
dealing with operator new.

> FAIL: g++.dg/vect/pr64410.cc  -std=c++17  scan-tree-dump vect "vectorized 1 
> loops in function"
> FAIL: g++.dg/vect/pr64410.cc  -std=c++26  scan-tree-dump vect "vectorized 1 
> loops in function"
> FAIL: gfortran.dg/guality/arg1.f90   -O3 -fomit-frame-pointer -funroll-loops 
> -fpeel-loops -ftracer -finline-functions  line 14 a(10) == 10



> FAIL: gfortran.dg/specifics_1.f90   -O2  execution test
> FAIL: gfortran.dg/specifics_1.f90   -O3 -fomit-frame-pointer -funroll-loops 
> -fpeel-loops -ftracer -finline-functions  execution test
> FAIL: gfortran.dg/specifics_1.f90   -O3 -g  execution test

The specifics_1 failure is a front-end bug which is being fixed:
https://gcc.gnu.org/pipermail/gcc-patches/2025-May/684016.html .

>
> with GCC configured with
>
> ../../gcc/configure 
> --prefix=/export/users/haochenj/src/gcc-bisect/master/master/r16-372/usr 
> --enable-clocale=gnu --with-system-zlib --with-demangler-in-ld 
> --with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet --without-isl 
> --enable-libmpx x86_64-linux --disable-bootstrap
>
> To reproduce:
>
> $ cd {build_dir}/gcc && make check 
> RUNTESTFLAGS="tree-ssa.exp=gcc.dg/tree-ssa/gen-vect-28.c 
> --target_board='unix{-m32}'"
> $ cd {build_dir}/gcc && make check 
> RUNTESTFLAGS="tree-ssa.exp=gcc.dg/tree-ssa/gen-vect-28.c 
> --target_board='unix{-m32\ -march=cascadelake}'"
> $ cd {build_dir}/gcc && make check 
> RUNTESTFLAGS="tree-ssa.exp=gcc.dg/tree-ssa/pr81627.c 
> --target_board='unix{-m32}'"
> $ cd {build_dir}/gcc && make check 
> RUNTESTFLAGS="tree-ssa.exp=gcc.dg/tree-ssa/pr81627.c 
> --target_board='unix{-m32\ -march=cascadelake}'"
> $ cd {build_dir}/gcc && make check 
> RUNTESTFLAGS="tree-ssa.exp=gcc.dg/tree-ssa/pr81627.c 
> --target_board='unix{-m64}'"
> $ cd {build_dir}/gcc && make check 
> RUNTESTFLAGS="tree-ssa.exp=gcc.dg/tree-ssa/pr81627.c 
> --target_board='unix{-m64\ -march=cascadelake}'"
> $ cd {build_dir}/gcc && make check 
> RUNTESTFLAGS="i386.exp=gcc.target/i386/avx512vl-vpmovuswb-2.c 
> --target_board='unix{-m32}'"
> $ cd {build_dir}/gcc && make check 
> RUNTESTFLAGS="i386.exp=gcc.target/i386/avx512vl-vpmovuswb-2.c 
> --target_board='unix{-m32\ -march=cascadelake}'"
> $ cd {build_dir}/gcc && make check 
> RUNTESTFLAGS="i386.exp=gcc.target/i386/avx512vl-vpmovuswb-2.c 
> --target_board='unix{-m64}'"
> $ cd {build_dir}/gcc && make check 
> RUNTESTFLAGS="i386.exp=gcc.target/i386/avx512vl-vpmovuswb-2.c 
> --target_board='unix{-m64\ -march=cascadelake}'"
> $ cd {build_dir}/gcc && make check 
> RUNTESTFLAGS="i386.exp=gcc.target/i386/avx512vl-vpmovwb-2.c 
> --target_board='unix{-m32}'"
> $ cd {build_dir}/gcc && make check 
> RUNTESTFLAGS="i386.exp=gcc.target/i386/avx512vl-vpmovwb-2.c 
> --target_board='unix{-m32\ -march=cascadelake}'"
> $ cd {build_dir}/gcc && make check 
> RUNTESTFLAGS="i386.exp=gcc.target/i386/avx512vl-vpmovwb-2.c 
> --target_board='unix{-m64}'"
> $ cd {build_dir}/gcc && make check 
> RUNTESTFLAGS="i386.exp=gcc.target/i386/avx512vl-vpmovwb-2.c 
> --target_board='unix{-m64\ -march=cascadelake}'"
> $ cd {build_dir}/gcc && make check 
> RUNTESTFLAGS="coro-torture.exp=g++.dg/coroutines/torture/exceptions-test-01-n4849-a.C
>  --target_board='unix{-m32}'"
> $ cd {build_dir}/gcc && make check 
> RUNTESTFLAGS="coro-torture.exp=g++.dg/coroutines/torture/exceptions-test-01-n4849-a.C
>  --target_board='unix{-m32\ -march=cascadelake}'"
> $ cd {build_dir}/gcc && make check 
> R