This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug debug/53363] New: g++.dg/debug/dwarf2/thunk1.C FAILs
- From: "ro at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 15 May 2012 15:38:13 +0000
- Subject: [Bug debug/53363] New: g++.dg/debug/dwarf2/thunk1.C FAILs
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53363
Bug #: 53363
Summary: g++.dg/debug/dwarf2/thunk1.C FAILs
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: debug
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: ro@gcc.gnu.org
CC: jason@gcc.gnu.org
Host: i386-pc-solaris2.*, i686-unknown-linux-gnu,
i386-apple-darwin11.3.0
Target: i386-pc-solaris2.*, i686-unknown-linux-gnu,
i386-apple-darwin11.3.0
Build: i386-pc-solaris2.*, i686-unknown-linux-gnu,
i386-apple-darwin11.3.0
The new g++.dg/debug/dwarf2/thunk1.C test FAILs in various configurations, e.g.
i386-pc-solaris2.*:
FAIL: g++.dg/debug/dwarf2/thunk1.C scan-assembler-times LFB3 1
FAIL: g++.dg/debug/dwarf2/thunk1.C scan-assembler-times LFB3 1
both for 32 and 64-bit tests.
i686-unknown-linux-gnu:
64-bit test only.
In the 32-bit Solaris/x86 case, LFB3 occurs 5 times:
.LFB3:
.long .LFB3
.long .LFE3-.LFB3
.long .LFB3@GOTOFF
.long .LFE3-.LFB3
In the 64-bit case, it doesn't occur at all.
I cannot tell for sure what the intent is: should this test only run for
32-bit?
Rainer