https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100467
Bug ID: 100467
Summary: [12 regression] g++.dg/debug/dwarf2/thunk1.C
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
CC: edlinger at gcc dot gnu.org
Target Milestone: ---
Target: i?86-*-*, x86_64-*-*
Between 20210505 (b927ffdd6cecd0eeda6ef77df2623519870b1e75) and 20210506
(07dd185755a791ab19e6a63274cf2cb69f087a6c),
the g++.dg/debug/dwarf2/thunk1.C test regressed:
+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
I'm seeing this on 32-bit Solaris/x86, but there are also reports for
Linux/x86.
This is most likely due to
commit e69ac0203725fb8da83a1cc88d32191b7a0b2c0c
Author: Bernd Edlinger <[email protected]>
Date: Tue Jan 12 16:27:53 2021 +0100
Add line debug info for virtual thunks
the number of LFB3 instances increased from the expected 5 to 8.
