On Linux/x86_64,
e69ac0203725fb8da83a1cc88d32191b7a0b2c0c is the first bad commit
commit e69ac0203725fb8da83a1cc88d32191b7a0b2c0c
Author: Bernd Edlinger <bernd.edlin...@hotmail.de>
Date: Tue Jan 12 16:27:53 2021 +0100
Add line debug info for virtual thunks
caused
FAIL: g++.dg/debug/dwarf2/thunk1.C -std=gnu++14 scan-assembler-times LFB3 5
FAIL: g++.dg/debug/dwarf2/thunk1.C -std=gnu++17 scan-assembler-times LFB3 5
FAIL: g++.dg/debug/dwarf2/thunk1.C -std=gnu++2a scan-assembler-times LFB3 5
FAIL: g++.dg/debug/dwarf2/thunk1.C -std=gnu++98 scan-assembler-times LFB3 5
with GCC configured with
../../gcc/configure
--prefix=/local/skpandey/gccwork/toolwork/gcc-bisect-master/master/r12-574/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="dwarf2.exp=g++.dg/debug/dwarf2/thunk1.C
--target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check
RUNTESTFLAGS="dwarf2.exp=g++.dg/debug/dwarf2/thunk1.C
--target_board='unix{-m32\ -march=cascadelake}'"
(Please do not reply to this email, for question about this report, contact me
at skpgkp2 at gmail dot com)
