From: Joel Brobecker <brobecker@gnat.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: a value has-a location
Date: Tue, 02 Nov 2004 15:32:00 -0000 [thread overview]
Message-ID: <20041102153252.GM27334@gnat.com> (raw)
In-Reply-To: <4187A414.5060804@gnu.org>
> I intend refactoring ``struct value'' so that there is an explicit
> location object (at present it's a union :-/). Initially it will
> probably remain in ``struct value''. Once the location has been
> separated out we can look at making it virtual with separate dwarf-2 and
> legacy locations.
Looks good. I didn't comment on making struct value opaque, but I think
it's a terrific idea. I think we should be doing the same for struct
type, and possible struct symbol/minimal_symbol/partial_symbol as well.
And heck, we could do the same for the symtab structs as well. That
would probably help us with transforming the low/high address range
into a set of ranges, for the compilation units that are not contiguous
in memory (a long term project of mine).
--
Joel
next prev parent reply other threads:[~2004-11-02 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-02 15:14 Andrew Cagney
2004-11-02 15:32 ` Joel Brobecker [this message]
2005-02-07 20:17 ` Andrew Cagney
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=20041102153252.GM27334@gnat.com \
--to=brobecker@gnat.com \
--cc=cagney@gnu.org \
--cc=gdb@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