From: Jim Blandy <jimb@redhat.com>
To: gdb@sources.redhat.com
Subject: implementing full scattered values
Date: Tue, 14 Sep 2004 15:39:00 -0000 [thread overview]
Message-ID: <vt2k6uw6eti.fsf@zenia.home> (raw)
Last month there was a thread on supporting DW_OP_piece:
http://sources.redhat.com/ml/gdb/2004-08/msg00004.html
Everyone agreed that having architecture-independent support for
arbitrary DW_OP_piece location expressions would be preferable to the
partial and architecture-dependent support, if someone could find time
to do it soon.
Let's talk about full scattered value support. What's the best
approach? What's entailed? How do we want 'struct value' to look
when we're done? Let's try to set some concrete goals so that if
someone does have the cycles to work on this, they can have some idea
what to work towards so it'll be acceptable for inclusion in the
public sources.
next reply other threads:[~2004-09-14 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 15:39 Jim Blandy [this message]
2004-09-14 17:57 ` 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=vt2k6uw6eti.fsf@zenia.home \
--to=jimb@redhat.com \
--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