From: Tom Tromey <tromey@redhat.com>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: dje@google.com (Doug Evans), gdb-patches@sourceware.org
Subject: Re: [10/15] Basic value access routines
Date: Wed, 24 Jun 2009 15:31:00 -0000 [thread overview]
Message-ID: <m3prctir7f.fsf@fleche.redhat.com> (raw)
In-Reply-To: <200906151658.n5FGwrN6026829@d12av02.megacenter.de.ibm.com> (Ulrich Weigand's message of "Mon\, 15 Jun 2009 18\:58\:53 +0200 \(CEST\)")
>>>>> "Ulrich" == Ulrich Weigand <uweigand@de.ibm.com> writes:
Ulrich> Those are additional minor issues; the type structures are indeed
Ulrich> space critical
I have been curious about this.
It seems to me that in a given gdb session, most types will not
actually be needed. (I haven't done the experiment though.)
If that is so, then it further seems to me that types would only be
space critical if we are instantiating them too eagerly. This has
lead me to wonder whether lazy instantiation of types would be
beneficial.
A related idea that occurred to me is that, with Jan's type GC, we
could detach types from objfiles and "intern" them (something like
bcache-for-types). This would only be a win if there are many
identical types distributed across objfiles, though.
Tom
next prev parent reply other threads:[~2009-06-24 15:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 15:20 Ulrich Weigand
2009-06-15 16:35 ` Doug Evans
2009-06-15 16:59 ` Ulrich Weigand
2009-06-22 20:32 ` Per-type architecture (Re: [10/15] Basic value access routines) Ulrich Weigand
2009-06-22 20:59 ` Daniel Jacobowitz
2009-06-23 0:41 ` Ulrich Weigand
2009-06-23 13:49 ` Daniel Jacobowitz
2009-06-23 14:02 ` Pedro Alves
2009-06-23 17:06 ` Ulrich Weigand
2009-06-23 17:30 ` Daniel Jacobowitz
2009-06-23 15:55 ` Doug Evans
2009-06-23 16:42 ` Mark Kettenis
2009-06-23 16:53 ` Daniel Jacobowitz
2009-06-23 16:57 ` Ulrich Weigand
2009-06-23 17:36 ` Doug Evans
2009-06-24 15:31 ` Tom Tromey [this message]
2009-06-24 15:46 ` [10/15] Basic value access routines Daniel Jacobowitz
2009-06-24 16:26 ` Doug Evans
2009-06-24 19:41 ` 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=m3prctir7f.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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