Regressions on master at commit r15-653 vs commit r15-634 on Linux/x86_64

[Haochen Jiang via Gcc-regression]

Regressions on master at commit r15-653 vs commit r15-634 on Linux/x86_64
New failures:
FAIL: 30_threads/future/members/poll.cc  -std=gnu++17 execution test

New passes:

[r15-579 Regression] FAIL: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/acc_prof-kernels-1.c -DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 -foffload=disable -O2 (test for excess errors) on Linux/x86_64

[Jiang, Haochen via Gcc-regression]

On Linux/x86_64,

a9251ab3c91c8c559d0306838575a666ae62dff4 is the first bad commit
commit a9251ab3c91c8c559d0306838575a666ae62dff4
Author: Richard Biener 
Date:   Thu May 16 12:35:28 2024 +0200

wrong code with points-to and volatile

caused


with GCC configured with

../../gcc/configure 
--prefix=/export/users/haochenj/src/gcc-bisect/master/master/r15-579/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}/x86_64-linux/libgomp/testsuite && make check 
RUNTESTFLAGS="c++.exp=libgomp.oacc-c-c++-common/acc_prof-kernels-1.c 
--target_board='unix{-m32}'"
$ cd {build_dir}/x86_64-linux/libgomp/testsuite && make check 
RUNTESTFLAGS="c++.exp=libgomp.oacc-c-c++-common/acc_prof-kernels-1.c 
--target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/x86_64-linux/libgomp/testsuite && make check 
RUNTESTFLAGS="c++.exp=libgomp.oacc-c-c++-common/acc_prof-kernels-1.c 
--target_board='unix{-m64}'"
$ cd {build_dir}/x86_64-linux/libgomp/testsuite && make check 
RUNTESTFLAGS="c++.exp=libgomp.oacc-c-c++-common/acc_prof-kernels-1.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.)

Regressions on master at commit r15-655 vs commit r15-653 on Linux/x86_64

[Haochen Jiang via Gcc-regression]

Regressions on master at commit r15-655 vs commit r15-653 on Linux/x86_64
New failures:

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

Regressions on native/master at commit r15-656 vs commit r15-655 on Linux/x86_64

[Haochen Jiang via Gcc-regression]

Regressions on master at commit r15-656 vs commit r15-655 on Linux/x86_64
New failures:

New passes:
FAIL: gcc.target/i386/avx512er-vrcp28ps-4.c scan-assembler-times 
vrcp28ps[^\n\r]*zmm[0-9]+(?:\n|[ \\t]+#) 1
FAIL: gcc.target/i386/avx512er-vrcp28ps-4.c scan-assembler-times 
vrcp28ps[^\n\r]*zmm[0-9]+(?:\n|[ \\t]+#) 1
FAIL: gcc.target/i386/avx512er-vrsqrt28ps-4.c scan-assembler-times 
vrsqrt28ps[^\n\r]*zmm[0-9]+(?:\n|[ \\t]+#) 1
FAIL: gcc.target/i386/avx512er-vrsqrt28ps-4.c scan-assembler-times 
vrsqrt28ps[^\n\r]*zmm[0-9]+(?:\n|[ \\t]+#) 1
FAIL: gcc.target/i386/avx512er-vrsqrt28ps-6.c scan-assembler-times 
vrcp28ps[^\n\r]*zmm[0-9]+(?:\n|[ \\t]+#) 1
FAIL: gcc.target/i386/avx512er-vrsqrt28ps-6.c scan-assembler-times 
vrcp28ps[^\n\r]*zmm[0-9]+(?:\n|[ \\t]+#) 1
FAIL: gcc.target/i386/avx512er-vrsqrt28ps-6.c scan-assembler-times 
vrsqrt28ps[^\n\r]*zmm[0-9]+(?:\n|[ \\t]+#) 1
FAIL: gcc.target/i386/avx512er-vrsqrt28ps-6.c scan-assembler-times 
vrsqrt28ps[^\n\r]*zmm[0-9]+(?:\n|[ \\t]+#) 1
FAIL: g++.target/i386/mv28.C  -std=c++14  (test for errors, line 16)
FAIL: g++.target/i386/mv28.C  -std=c++14  (test for errors, line 16)
FAIL: g++.target/i386/mv28.C  -std=c++14  (test for errors, line 17)
FAIL: g++.target/i386/mv28.C  -std=c++14  (test for errors, line 17)
FAIL: g++.target/i386/mv28.C  -std=c++14  (test for errors, line 18)
FAIL: g++.target/i386/mv28.C  -std=c++14  (test for errors, line 18)
FAIL: g++.target/i386/mv28.C  -std=c++14  (test for errors, line 19)
FAIL: g++.target/i386/mv28.C  -std=c++14  (test for errors, line 19)
FAIL: g++.target/i386/mv28.C  -std=c++17  (test for errors, line 16)
FAIL: g++.target/i386/mv28.C  -std=c++17  (test for errors, line 16)
FAIL: g++.target/i386/mv28.C  -std=c++17  (test for errors, line 17)
FAIL: g++.target/i386/mv28.C  -std=c++17  (test for errors, line 17)
FAIL: g++.target/i386/mv28.C  -std=c++17  (test for errors, line 18)
FAIL: g++.target/i386/mv28.C  -std=c++17  (test for errors, line 18)
FAIL: g++.target/i386/mv28.C  -std=c++17  (test for errors, line 19)
FAIL: g++.target/i386/mv28.C  -std=c++17  (test for errors, line 19)
FAIL: g++.target/i386/mv28.C  -std=c++20  (test for errors, line 16)
FAIL: g++.target/i386/mv28.C  -std=c++20  (test for errors, line 16)
FAIL: g++.target/i386/mv28.C  -std=c++20  (test for errors, line 17)
FAIL: g++.target/i386/mv28.C  -std=c++20  (test for errors, line 17)
FAIL: g++.target/i386/mv28.C  -std=c++20  (test for errors, line 18)
FAIL: g++.target/i386/mv28.C  -std=c++20  (test for errors, line 18)
FAIL: g++.target/i386/mv28.C  -std=c++20  (test for errors, line 19)
FAIL: g++.target/i386/mv28.C  -std=c++20  (test for errors, line 19)
FAIL: g++.target/i386/mv28.C  -std=c++98  (test for errors, line 16)
FAIL: g++.target/i386/mv28.C  -std=c++98  (test for errors, line 16)
FAIL: g++.target/i386/mv28.C  -std=c++98  (test for errors, line 17)
FAIL: g++.target/i386/mv28.C  -std=c++98  (test for errors, line 17)
FAIL: g++.target/i386/mv28.C  -std=c++98  (test for errors, line 18)
FAIL: g++.target/i386/mv28.C  -std=c++98  (test for errors, line 18)
FAIL: g++.target/i386/mv28.C  -std=c++98  (test for errors, line 19)
FAIL: g++.target/i386/mv28.C  -std=c++98  (test for errors, line 19)