[r16-5628 Regression] FAIL: g++.target/i386/vect-pragma-target-2.C -std=gnu++20 (test for excess errors) on Linux/x86_64
Haochen Jiang via Gcc-regression <[email protected]>
| Newsgroups | gmane.comp.gcc.regression,gmane.comp.gcc.patches |
|---|---|
| Message-ID | <[email protected]> |
On Linux/x86_64, 004438857554f47eb5491d59b067e56fdacf0e74 is the first bad commit commit 004438857554f47eb5491d59b067e56fdacf0e74 Author: Jakub Jelinek <[email protected]> Date: Wed Nov 26 15:01:11 2025 +0100 Change the default C++ dialect to gnu++20 caused FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers.C -std=c++20 at line 12 (test for warnings, line 11) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers.C -std=c++20 telltale event that we are going within a deeper frame than 'main' (test for warnings, line 9) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers.C -std=c++20 (test for excess errors) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers.C -std=c++26 at line 12 (test for warnings, line 11) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers.C -std=c++26 telltale event that we are going within a deeper frame than 'main' (test for warnings, line 9) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers.C -std=c++26 (test for excess errors) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-default.C -std=c++14 at line 12 (test for warnings, line 11) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-default.C -std=c++14 at line 17 (test for warnings, line 10) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-default.C -std=c++14 at line 18 (test for warnings, line 11) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-default.C -std=c++14 at line 19 (test for warnings, line 11) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-default.C -std=c++14 at line 20 (test for warnings, line 11) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-default.C -std=c++20 at line 12 (test for warnings, line 11) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-default.C -std=c++20 at line 18 (test for warnings, line 11) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-default.C -std=c++20 at line 19 (test for warnings, line 11) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-default.C -std=c++20 at line 20 (test for warnings, line 11) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-no.C -std=c++14 at line 13 (test for warnings, line 12) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-no.C -std=c++14 at line 18 (test for warnings, line 11) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-no.C -std=c++14 at line 19 (test for warnings, line 12) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-no.C -std=c++14 at line 20 (test for warnings, line 12) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-no.C -std=c++14 at line 21 (test for warnings, line 12) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-no.C -std=c++20 at line 13 (test for warnings, line 12) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-no.C -std=c++20 at line 19 (test for warnings, line 12) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-no.C -std=c++20 at line 20 (test for warnings, line 12) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-no.C -std=c++20 at line 21 (test for warnings, line 12) FAIL: g++.dg/ipa/devirt-2.C -std=gnu++20 scan-ipa-dump cp "Discovered a virtual call to a known target.*B::foo" FAIL: g++.dg/ipa/devirt-2.C -std=gnu++26 scan-ipa-dump cp "Discovered a virtual call to a known target.*B::foo" FAIL: g++.dg/ipa/devirt-2.C -std=gnu++98 scan-ipa-dump cp "Discovered a virtual call to a known target.*B::foo" FAIL: g++.target/i386/vect-pragma-target-2.C -std=gnu++20 (test for excess errors) FAIL: g++.target/i386/vect-pragma-target-2.C -std=gnu++26 (test for excess errors) FAIL: g++.target/i386/vect-pragma-target-2.C -std=gnu++98 (test for excess errors) with GCC configured with ../../gcc/configure --prefix=/export/users3/haochenj/src/gcc-bisect/master/master/r16-5628/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="analyzer.exp=g++.dg/analyzer/fanalyzer-show-events-in-system-headers.C --target_board='unix{-m32}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="analyzer.exp=g++.dg/analyzer/fanalyzer-show-events-in-system-headers.C --target_board='unix{-m32\ -march=cascadelake}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="analyzer.exp=g++.dg/analyzer/fanalyzer-show-events-in-system-headers.C --target_board='unix{-m64}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="analyzer.exp=g++.dg/analyzer/fanalyzer-show-events-in-system-headers.C --target_board='unix{-m64\ -march=cascadelake}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="analyzer.exp=g++.dg/analyzer/fanalyzer-show-events-in-system-headers-default.C --target_board='unix{-m32}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="analyzer.exp=g++.dg/analyzer/fanalyzer-show-events-in-system-headers-default.C --target_board='unix{-m32\ -march=cascadelake}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="analyzer.exp=g++.dg/analyzer/fanalyzer-show-events-in-system-headers-default.C --target_board='unix{-m64}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="analyzer.exp=g++.dg/analyzer/fanalyzer-show-events-in-system-headers-default.C --target_board='unix{-m64\ -march=cascadelake}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="analyzer.exp=g++.dg/analyzer/fanalyzer-show-events-in-system-headers-no.C --target_board='unix{-m32}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="analyzer.exp=g++.dg/analyzer/fanalyzer-show-events-in-system-headers-no.C --target_board='unix{-m32\ -march=cascadelake}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="analyzer.exp=g++.dg/analyzer/fanalyzer-show-events-in-system-headers-no.C --target_board='unix{-m64}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="analyzer.exp=g++.dg/analyzer/fanalyzer-show-events-in-system-headers-no.C --target_board='unix{-m64\ -march=cascadelake}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=g++.dg/ipa/devirt-2.C --target_board='unix{-m32}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=g++.dg/ipa/devirt-2.C --target_board='unix{-m32\ -march=cascadelake}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=g++.dg/ipa/devirt-2.C --target_board='unix{-m64}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=g++.dg/ipa/devirt-2.C --target_board='unix{-m64\ -march=cascadelake}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=g++.target/i386/vect-pragma-target-2.C --target_board='unix{-m32\ -march=cascadelake}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=g++.target/i386/vect-pragma-target-2.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.)