[r17-2404 Regression] FAIL: c-c++-common/gomp/reverse-offload-1.c -std=c++98 scan-tree-dump-times omplower "omp declare target[^ ]" 3 on Linux/x86_64
Haochen Jiang <[email protected]> Wed, 15 Jul 2026 18:49:41 +0800
| Newsgroups | gmane.comp.gcc.patches,gmane.comp.gcc.regression |
|---|---|
| Message-ID | <[email protected]> |
On Linux/x86_64, 2468c79741f97c2aa0cbb4baaccb86fd4a150910 is the first bad commit commit 2468c79741f97c2aa0cbb4baaccb86fd4a150910 Author: Tobias Burnus <[email protected]> Date: Wed Jul 15 08:43:26 2026 +0200 OpenMP: Handle 'device_type(host)' on 'target' caused FAIL: c-c++-common/gomp/reverse-offload-1.c scan-tree-dump-times omplower "omp declare target[^ ]" 3 FAIL: c-c++-common/gomp/reverse-offload-1.c -std=c++20 scan-tree-dump-times omplower "omp declare target[^ ]" 3 FAIL: c-c++-common/gomp/reverse-offload-1.c -std=c++29 scan-tree-dump-times omplower "omp declare target[^ ]" 3 FAIL: c-c++-common/gomp/reverse-offload-1.c -std=c++98 scan-tree-dump-times omplower "omp declare target[^ ]" 3 with GCC configured with ../../gcc/configure --prefix=/export/users3/haochenj/src/gcc-bisect/master/master/r17-2404/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="gomp.exp=c-c++-common/gomp/reverse-offload-1.c --target_board='unix{-m32}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="gomp.exp=c-c++-common/gomp/reverse-offload-1.c --target_board='unix{-m32\ -march=cascadelake}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="gomp.exp=c-c++-common/gomp/reverse-offload-1.c --target_board='unix{-m64}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="gomp.exp=c-c++-common/gomp/reverse-offload-1.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.)