Re: [r16-8385 Regression] FAIL: g++.dg/modules/compile-std1.C -std=c++26 (test for excess errors) on Linux/x86_64
Jonathan Wakely via Gcc-regression <[email protected]>
| Newsgroups | gmane.comp.gcc.regression,gmane.comp.gcc.patches |
|---|---|
| Message-ID | <CACb0b4kGG0Xhhe6+21cODJTdc0A-3HK=Ws7NR3eXk0Sv3M1qMg@mail.gmail.com> |
This is already fixed. On Thu, 2 Apr 2026 at 09:18, Haochen Jiang <[email protected]> wrote: > > On Linux/x86_64, > > c9525a790291bb924ac5d9887dd1f57e76a66a03 is the first bad commit > commit c9525a790291bb924ac5d9887dd1f57e76a66a03 > Author: Jonathan Wakely <[email protected]> > Date: Mon Mar 30 12:13:39 2026 +0100 > > libstdc++: Rename saturation arithmetic for C++26 (P4052R0) > > caused > > FAIL: g++.dg/modules/compile-std1.C module-cmi std.compat (gcm.cache/std.compat.gcm) > FAIL: g++.dg/modules/compile-std1.C module-cmi std (gcm.cache/std.gcm) > FAIL: g++.dg/modules/compile-std1.C -std=c++26 (test for excess errors) > > with GCC configured with > > ../../gcc/configure --prefix=/export/users3/haochenj/src/gcc-bisect/master/master/r16-8385/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="modules.exp=g++.dg/modules/compile-std1.C --target_board='unix{-m32}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="modules.exp=g++.dg/modules/compile-std1.C --target_board='unix{-m32\ -march=cascadelake}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="modules.exp=g++.dg/modules/compile-std1.C --target_board='unix{-m64}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="modules.exp=g++.dg/modules/compile-std1.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.) >