From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb@sources.redhat.com, gcc-bugs@gcc.gnu.org
Subject: More libiberty/demangler fallout - gdb (was: Re: Er, ...)
Date: Thu, 31 Jan 2002 09:59:00 -0000 [thread overview]
Message-ID: <20020131125948.A12285@nevyn.them.org> (raw)
In-Reply-To: <3C59819D.9020500@cygnus.com>
On Thu, Jan 31, 2002 at 12:40:45PM -0500, Andrew Cagney wrote:
> Er, the number of failures on NetBSD/PPC just jumped from ~147 to ~650.
> This segment of bitfields.c illustrates the problem. I don't think it
> is my cleanups here :-/
>
> ac131313@nettle$ gcc --version
> egcs-1.1.2
>
> Generates stabs in elf.
(You scared me! bitfields.c has nothing to do with the problem :)
The problem is:
> (gdb) print/x flags
> $11 = {uc = 0xff, s1 = 0x0, u1 = 0x1, s2 = 0x0, u2 = 0x3, s3 = 0x0, u3 =
> 0x7, s9 = 0x0, u
> 9 = 0x1ff, sc = 0x0}
> (gdb) PASS: gdb.base/bitfields.exp: bitfield containment #1
>
>
> (gdb) print/x flags
> $11 = {uc = 0xff, short = 0x0, u1 = 0x1, short = 0x0, u2 = 0x3, short =
> 0x0, u3
> = 0x7, short = 0x0, u9 = 0x1ff, short = 0x0}
> (gdb) FAIL: gdb.base/bitfields.exp: bitfield containment #1
All the 's1's have been replaced by 'short'. This is because of the
current argument on one of the gcc lists about how the demangler should
treat symbols that may be mangled but without the leading mangling
prefix for v3 mangling.
GCC folks, can we please get this fixed?
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-01-31 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-31 9:40 Er, Andrew Cagney
2002-01-31 9:59 ` Daniel Jacobowitz [this message]
2002-01-31 10:10 ` More libiberty/demangler fallout - gdb (was: Re: Er, ...) Andrew Cagney
2002-01-31 10:46 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020131125948.A12285@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@cygnus.com \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox