This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug testsuite/29307] New: libiberty/testsuite/test-demangle : parsing errors after unknown demangling style
- From: "phil dot lello at homecall dot co dot uk" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 1 Oct 2006 14:45:26 -0000
- Subject: [Bug testsuite/29307] New: libiberty/testsuite/test-demangle : parsing errors after unknown demangling style
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
When running libiberty/testsuite/test-demangle with an unknown demangling
style, parsing gets confused...
NOTE: I came accross this while investigating adding support for vc-style
mangling to libiberty, so failure is expected, but the "unknown demangling
style" for lines other than the "--format=msvc" is misleading.
Input:
# Symbols from C:\WINDOWS\$hf_mig$\KB896358\SP2QFE\hhsetup.dll
--format=msvc --no-params
??0CFIFOString@@QAE@XZ
public: __thiscall CFIFOString::CFIFOString(void)
CFIFOString::CFIFOString
#
--format=msvc --no-params
??0CPointerList@@QAE@XZ
public: __thiscall CPointerList::CPointerList(void)
CPointerList::CPointerList
Output:
FAIL at line 4: unknown demangling style msvc
FAIL at line 4, options --format=msvc:
in: ??0CFIFOString@@QAE@XZ
out: (null)
exp: public: __thiscall CFIFOString::CFIFOString(void)
FAIL at line 8: unknown demangling style CFIFOString::CFIFOString
FAIL at line 11: unknown demangling style public: __thiscall
CPointerList::CPointerList(void)
test-demangle: 3 tests, 4 failures
--
Summary: libiberty/testsuite/test-demangle : parsing errors after
unknown demangling style
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: trivial
Priority: P3
Component: testsuite
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: phil dot lello at homecall dot co dot uk
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29307