Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: Elena Zannoni <ezannoni@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [rfa] Add SYMBOL_SET_LINKAGE_NAME
Date: Tue, 17 Feb 2004 15:57:00 -0000	[thread overview]
Message-ID: <403239F3.70003@gnu.org> (raw)
In-Reply-To: <20040216225743.GA1714@nevyn.them.org>

> On Mon, Feb 16, 2004 at 04:48:57PM -0500, Elena Zannoni wrote:
> 
>> Daniel Jacobowitz writes:
>>  > After this patch and my others from today there are no direct
>>  > assignments to the symbol name. In addition to the cleanup value, I'm
>>  > testing an approach which would change the storage of symbol names,
>>  > which prompted me to do this.  
>> 
>> can you elaborate on where you are going?
> 
> 
> Sure.  I'm not sure if it's actually going to end up this way, since
> I'm thinking it wasn't a great idea and it has some truly gross bits I
> haven't figured out what to do with yet - it was just a hack job last
> weekend.  But here's what my current tree does.
> 
> The C++ demangled name pointer in lang_specific is removed.  The name
> pointer becomes a union, and a flag bit (there's about a byte's worth
> of empty space in general_symbol_info) is added.  They look like this:

Er, why not start by defining a relevant interface and then work 
inwards?  That way potential clients, such as paulh, can determine if it 
is sufficient for their needs.  The first implementation doesn't even 
need to be fast, just correct.  Once we've hard data on the interfaces 
run-time behavioral characteristics we can consider symtab internal changes.

Andrew



  parent reply	other threads:[~2004-02-17 15:57 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-16 21:24 Daniel Jacobowitz
2004-02-16 21:53 ` Elena Zannoni
2004-02-16 22:57   ` Daniel Jacobowitz
2004-02-16 23:35     ` Paul Hilfinger
2004-02-17  0:05       ` Daniel Jacobowitz
2004-02-17  9:59         ` Paul N. Hilfinger
2004-02-17 15:57     ` Andrew Cagney [this message]
2004-02-17 16:01       ` Daniel Jacobowitz
2004-02-17 19:14         ` Elena Zannoni
2004-02-17 19:29           ` Daniel Jacobowitz
2004-02-17 23:10             ` Andrew Cagney
2004-02-18  0:43             ` Elena Zannoni
2004-02-18  1:04               ` Daniel Jacobowitz
2004-02-18  0:20 ` David Carlton
2004-02-18  0:23   ` Daniel Jacobowitz
2004-02-18  0:27     ` Elena Zannoni
2004-02-18  0:32       ` Daniel Jacobowitz
2004-02-18  0:54         ` Elena Zannoni
2004-02-18  1:06           ` Daniel Jacobowitz
2004-02-18  0:49   ` Paul Hilfinger
2004-02-18  1:27     ` David Carlton
2004-02-18  8:12       ` Paul N. Hilfinger
2004-02-18 16:45         ` David Carlton
2004-02-20  9:32           ` Paul N. Hilfinger

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=403239F3.70003@gnu.org \
    --to=cagney@gnu.org \
    --cc=drow@false.org \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@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