[r16-3810 Regression] FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-no.C -std=c++17 at line 21 (test for warnings, line 12) on Linux/x86_64
"Jiang, Haochen via Gcc-regression" <[email protected]>
| Newsgroups | gmane.comp.gcc.regression,gmane.comp.gcc.patches |
|---|---|
| Message-ID | <SJ5PPF77D28E3C23C9A0BF376E4234223C6EC08A@SJ5PPF77D28E3C2.namprd11.prod.outlook.com> |
On Linux/x86_64, 6456da6bab8a2c43e7899afda991589065d96595 is the first bad commit commit 6456da6bab8a2c43e7899afda991589065d96595 Author: Jonathan Wakely <[email protected]> Date: Thu Jul 17 22:02:45 2025 +0100 libstdc++: Make atomicity helpers use unsigned arithmetic [PR121148] caused FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers.C -std=c++17 at line 12 (test for warnings, line 11) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers.C -std=c++17 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++17 (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++17 at line 12 (test for warnings, line 11) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-default.C -std=c++17 at line 18 (test for warnings, line 11) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-default.C -std=c++17 at line 19 (test for warnings, line 11) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-default.C -std=c++17 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++17 at line 13 (test for warnings, line 12) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-no.C -std=c++17 at line 19 (test for warnings, line 12) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-no.C -std=c++17 at line 20 (test for warnings, line 12) FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-no.C -std=c++17 at line 21 (test for warnings, line 12) with GCC configured with ../../gcc/configure --prefix=/export/users3/haochenj/src/gcc-bisect/master/master/r16-3810/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}'" (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.)