From: Tom Tromey <tromey@redhat.com>
To: sami wagiaalla <swagiaal@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Change cplus_specific to an alocated struct
Date: Tue, 15 Jun 2010 22:56:00 -0000 [thread overview]
Message-ID: <m3pqzrucpg.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4C167FCA.7030300@redhat.com> (sami wagiaalla's message of "Mon, 14 Jun 2010 15:15:22 -0400")
>>>>> "Sami" == sami wagiaalla <swagiaal@redhat.com> writes:
Tom> It seems to me that soon we're going to want to add a bunch of
Tom> C++-specific fields, and we don't want to unnecessarily penalize the
Tom> other languages with our baggage.
Sami> I wasn't really planing one :D, but what do you think of this:
Sami> We leave the current struct as is and rename cplus_specific to
Sami> mangled_lang_specific (or just mangled_lang). And the the union we add
Sami> a cplus_specific that managed as things are in this patch, and is
Sami> actually cplus_specific ?
That sounds ok to me.
Sami> I think that is just a wrong use of lazy here. I meant to say
Sami> initialize it /if/ it is going to be used rather than when...
Sami> symbol_init_cplus_specific is called from symbol_set_names where the
Sami> bcache is updated.
Aha, thanks.
Tom
next prev parent reply other threads:[~2010-06-15 22:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 16:05 sami wagiaalla
2010-05-26 16:55 ` sami wagiaalla
2010-06-08 17:02 ` Tom Tromey
2010-06-14 19:29 ` sami wagiaalla
2010-06-15 22:56 ` Tom Tromey [this message]
2010-07-12 18:03 ` [patch 1/3] " sami wagiaalla
2010-07-13 17:16 ` Tom Tromey
2010-07-16 14:15 ` sami wagiaalla
2010-07-16 15:24 ` Tom Tromey
2010-07-12 18:06 ` [patch 2/3] " sami wagiaalla
2010-07-13 17:24 ` Tom Tromey
2010-07-16 14:15 ` sami wagiaalla
2010-07-12 18:08 ` [patch 3/3] " sami wagiaalla
2010-07-13 17:38 ` Tom Tromey
2010-07-16 14:15 ` sami wagiaalla
2010-07-16 15:29 ` Tom Tromey
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=m3pqzrucpg.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--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