From: Doug Evans <dje@google.com>
To: gdb-patches@sourceware.org, swagiaal@redhat.com,
sergiodj@redhat.com
Subject: Re: [PATCH] Remove general_symbol_info.language_specific.cplus_specific
Date: Wed, 03 Dec 2014 02:39:00 -0000 [thread overview]
Message-ID: <21630.30630.261031.207300@ruffy2.mtv.corp.google.com> (raw)
In-Reply-To: <yjt2sih6wrdh.fsf@ruffy.mtv.corp.google.com>
Doug Evans writes:
> Hi.
>
> This patch reverts the addition of cplus_specific added here:
>
> 2010-07-16 Sami Wagiaalla <swagiaal@redhat.com>
>
> * symtab.h (symbol_set_demangled_name): Now takes an optional objfile*
> argument.
> (cplus_specific): New struct.
> * symtab.c (symbol_set_demangled_name): Updated.
> Use cplus_specific for cplus symbols.
> (symbol_get_demangled_name): Retrive the name from the cplus_specific
> struct for cplus symbols.
> (symbol_init_language_specific): Set cplus_specific for cplus symbols.
> (symbol_set_names): Pass objfile to symbol_set_demangled_name.
> * symtab.c (symbol_init_cplus_specific): New function.
>
> It was added in anticipation of improved template support:
>
> https://sourceware.org/ml/gdb-patches/2010-05/msg00594.html
> https://sourceware.org/ml/gdb-patches/2010-07/msg00284.html
>
> However, minsyms pay the price for this space too.
> For my standard benchmark this patch gets back 44MB of memory
> when gdb starts. [There's still ~440MB of memory used
> by the demangled ELF symbols of this benchmark,
> but that's another topic.]
>
> When the improved templated support is added,
> I wonder if this can be moved to struct symbol.
> Hmmm, we already have a special version of
> struct symbol for templates (struct template_symbol).
>
> Regression tested on amd64-linux.
>
> 2014-11-25 Doug Evans <dje@google.com>
>
> * symtab.c (symbol_init_cplus_specific): Delete.
> (symbol_set_demangled_name): Remove special c++ support.
> (symbol_get_demangled_name, symbol_set_language): Ditto.
> * symtab.h (struct cplus_specific): Delete.
> (struct general_symbol_info) <language_specific>: Remove
> cplus_specific.
Committed.
prev parent reply other threads:[~2014-12-03 2:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 3:52 Doug Evans
2014-12-03 2:39 ` Doug Evans [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=21630.30630.261031.207300@ruffy2.mtv.corp.google.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.com \
--cc=swagiaal@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).