From: Daniel Jacobowitz <drow@false.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: reference counting for value
Date: Tue, 07 Jul 2009 14:59:00 -0000 [thread overview]
Message-ID: <20090707145930.GA18388@caradoc.them.org> (raw)
In-Reply-To: <m3iqi4r2mv.fsf@fleche.redhat.com>
On Tue, Jul 07, 2009 at 08:25:44AM -0600, Tom Tromey wrote:
> Another idea I've been kicking around a bit is to also reference count
> the contents. This would solve this particular problem without
> needing a bitfield->parent reference, as the two would just share some
> structure.
Would it? We need to be able to fetch the contents in response to a
request from the bitfield, so everything needed to unlazy would
have to be in the shared structure; I guess that's address and length,
here. Also lval type. Would we have to duplicate these in the value
and the shared contents?
If two values have a shared contents structure, I'm not sure what
point there is having them different value structures in the first place.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-07-07 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 20:26 Tom Tromey
2009-07-07 1:49 ` Daniel Jacobowitz
2009-07-07 14:26 ` Tom Tromey
2009-07-07 14:59 ` Daniel Jacobowitz [this message]
2009-07-07 17:03 ` 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=20090707145930.GA18388@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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