From: Andrew Cagney <ac131313@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>, gdb@sources.redhat.com
Cc: Daniel Jacobowitz <drow@mvista.com>, gcc-bugs@gcc.gnu.org
Subject: Re: More libiberty/demangler fallout - gdb (was: Re: Er, ...)
Date: Thu, 31 Jan 2002 10:46:00 -0000 [thread overview]
Message-ID: <3C599106.9080706@cygnus.com> (raw)
In-Reply-To: <3C598876.9060506@cygnus.com>
> 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?
>
>
> Ah, thanks. I think I'll read up on GCC's revert rules.
http://gcc.gnu.org/develop.html (see Patch Reversion :-)
2002-01-30 Phil Edwards <pme@gcc.gnu.org>
* cp-demangle.c (cp_demangle_type): Do not protect with
IN_LIBGCC2.
(cplus_demangle_v3): Mimic __cxa_demangle and fall back on
cp_demangle_type.
* testsuite/demangle-expected: New gnu-v3 test.
For GDB people you want to drop liberty/cp-demangle.c back to 1.15 until
this clears up.
Andrew
prev parent reply other threads:[~2002-01-31 18:46 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 ` More libiberty/demangler fallout - gdb (was: Re: Er, ...) Daniel Jacobowitz
2002-01-31 10:10 ` Andrew Cagney
2002-01-31 10:46 ` Andrew Cagney [this message]
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=3C599106.9080706@cygnus.com \
--to=ac131313@cygnus.com \
--cc=drow@mvista.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