From: David Carlton <carlton@kealia.com>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: ian@wasabisystems.com, ac131313@redhat.com, drow@mvista.com,
gdb@sources.redhat.com, wcohen@redhat.com
Subject: Re: Slow handling of C++ symbol names
Date: Wed, 03 Dec 2003 16:52:00 -0000 [thread overview]
Message-ID: <yf28yltsv2b.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <20031203164734.201124B35B@berman.michael-chastain.com> (Michael Elizabeth Chastain's message of "Wed, 3 Dec 2003 11:47:34 -0500 (EST)")
On Wed, 3 Dec 2003 11:47:34 -0500 (EST), mec.gnu@mindspring.com (Michael Elizabeth Chastain) said:
> _ZStltI9file_pathSsEbRKSt4pairIT_T0_ES6_
> OLD: bool std::operator< <file_path, std::basic_string<char, std::char_traits<char>, std::allocator<char> > >(std::pair<file_path, std::basic_string<char, std::char_traits<char>, std::allocator<char> > > const&, std::pair<file_path, std::basic_string<char, > std::char_traits<char>, std::allocator<char> > > const&)
> NEW: bool std::operator<<file_path, std::string>(std::pair<file_path, std::string> const&, std::pair<file_path, std::string> const&)
Fascinating.
> The old demangler produces "operator< <", and the new demangler
> produces "operator <<". I'm not a name mangling expert but I think
> that "operator <" is correct here and the new demangler suffers from
> shift-operator-versus-template-syntax gotcha.
Yeah, that's a bug, even one which could cause problems for GDB.
David Carlton
carlton@kealia.com
next prev parent reply other threads:[~2003-12-03 16:52 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 16:48 Michael Elizabeth Chastain
2003-12-03 16:52 ` David Carlton [this message]
2003-12-03 16:58 ` Ian Lance Taylor
2003-12-03 17:08 ` Daniel Jacobowitz
2003-12-03 17:34 ` Ian Lance Taylor
2003-12-03 17:38 ` Daniel Jacobowitz
2003-12-03 17:54 ` Ian Lance Taylor
-- strict thread matches above, loose matches on Subject: below --
2003-12-03 22:30 Michael Elizabeth Chastain
2003-12-03 20:27 Michael Elizabeth Chastain
2003-12-03 20:35 ` Ian Lance Taylor
2003-12-03 20:17 Michael Elizabeth Chastain
2003-12-03 20:14 Michael Elizabeth Chastain
2003-12-03 19:57 Michael Elizabeth Chastain
2003-12-03 20:16 ` Daniel Jacobowitz
2003-12-02 22:38 Michael Elizabeth Chastain
2003-12-02 22:09 Michael Elizabeth Chastain
2003-12-02 22:23 ` Ian Lance Taylor
2003-12-02 22:29 ` Daniel Jacobowitz
2003-12-03 18:52 ` Andrew Cagney
[not found] <3FBBDC27.50204@redhat.com>
2003-11-19 21:13 ` Daniel Jacobowitz
2003-11-20 16:09 ` Andrew Cagney
2003-11-20 16:19 ` Daniel Jacobowitz
2003-11-20 16:54 ` Andrew Cagney
2003-11-20 16:58 ` Daniel Jacobowitz
2003-11-21 17:58 ` Daniel Jacobowitz
2003-11-26 14:27 ` Andrew Cagney
2003-11-26 16:24 ` Will Cohen
2003-11-26 20:48 ` Andrew Cagney
2003-11-26 20:45 ` Will Cohen
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=yf28yltsv2b.fsf@hawaii.kealia.com \
--to=carlton@kealia.com \
--cc=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=ian@wasabisystems.com \
--cc=mec.gnu@mindspring.com \
--cc=wcohen@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