Re: [r16-5792 Regression] FAIL: libgomp.c++/../libgomp.c-c++-common/requires-5.c (test for excess errors) on Linux/x86_64

On 02/12/2025 02:11, Jiang, Haochen wrote:
> On Linux/x86_64,
> 
> 723b18ce3dd24ebcbb6426fb40a375642477123f is the first bad commit
> commit 723b18ce3dd24ebcbb6426fb40a375642477123f
> Author: Andrew Stubbs <[email protected]>
> Date:   Thu Nov 20 17:18:13 2025 +0000
> 
>      libgomp, amdgcn: Implement Managed Memory
> 
> caused
> 
> 
> with GCC configured with
> 
> ../../gcc/configure --prefix=/export/users3/haochenj/src/gcc-bisect/master/master/r16-5792/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.c-c++-common/requires-4a.c --target_board='unix{-m32}'"
> $ cd {build_dir}/x86_64-linux/libgomp/testsuite && make check RUNTESTFLAGS="c++.exp=libgomp.c-c++-common/requires-4a.c --target_board='unix{-m32\ -march=cascadelake}'"
> $ cd {build_dir}/x86_64-linux/libgomp/testsuite && make check RUNTESTFLAGS="c++.exp=libgomp.c-c++-common/requires-4a.c --target_board='unix{-m64}'"
> $ cd {build_dir}/x86_64-linux/libgomp/testsuite && make check RUNTESTFLAGS="c++.exp=libgomp.c-c++-common/requires-4a.c --target_board='unix{-m64\ -march=cascadelake}'"
> $ cd {build_dir}/x86_64-linux/libgomp/testsuite && make check RUNTESTFLAGS="c++.exp=libgomp.c-c++-common/requires-4.c --target_board='unix{-m32}'"
> $ cd {build_dir}/x86_64-linux/libgomp/testsuite && make check RUNTESTFLAGS="c++.exp=libgomp.c-c++-common/requires-4.c --target_board='unix{-m32\ -march=cascadelake}'"
> $ cd {build_dir}/x86_64-linux/libgomp/testsuite && make check RUNTESTFLAGS="c++.exp=libgomp.c-c++-common/requires-4.c --target_board='unix{-m64}'"
> $ cd {build_dir}/x86_64-linux/libgomp/testsuite && make check RUNTESTFLAGS="c++.exp=libgomp.c-c++-common/requires-4.c --target_board='unix{-m64\ -march=cascadelake}'"
> $ cd {build_dir}/x86_64-linux/libgomp/testsuite && make check RUNTESTFLAGS="c++.exp=libgomp.c-c++-common/requires-5.c --target_board='unix{-m32}'"
> $ cd {build_dir}/x86_64-linux/libgomp/testsuite && make check RUNTESTFLAGS="c++.exp=libgomp.c-c++-common/requires-5.c --target_board='unix{-m32\ -march=cascadelake}'"
> $ cd {build_dir}/x86_64-linux/libgomp/testsuite && make check RUNTESTFLAGS="c++.exp=libgomp.c-c++-common/requires-5.c --target_board='unix{-m64}'"
> $ cd {build_dir}/x86_64-linux/libgomp/testsuite && make check RUNTESTFLAGS="c++.exp=libgomp.c-c++-common/requires-5.c --target_board='unix{-m64\ -march=cascadelake}'"
> 
> (Please directly reply to this email for question about this report.)
> (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.)

This should be fixed now.

The problem was a latent bug in the effective-target test.

Andrew