Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: interface to partial support for DW_OP_piece in dwarf2expr.[ch]
Date: Wed, 04 Aug 2004 18:26:00 -0000	[thread overview]
Message-ID: <vt2fz7292z3.fsf@zenia.home> (raw)
In-Reply-To: <4111145F.7000504@gnu.org>


Andrew Cagney <cagney@gnu.org> writes:
> I'm just having trouble getting my head around how this will affect
> core-gdb, and seeing how this addresses our need to meet GCC 3.5's
> requirements?
> 
> Can we expand on that?
>
> Looking at the below:
> 
> - a single value can have multiple locations (important for store)
> - could dwarf2_expr_piece be called ``struct location''? :-)

That's where we're heading, yes.  But I think one of the valuable
things about dwarf2expr.[ch] is that it does its job --- evaluating
Dwarf location expressions --- and only that job.  We ought to leave
the work of constructing GDB-specific data structures to its clients,
like dwarf2loc.c and dwarf2-frame.c.  That separation is important to
preserve; I see this as just another aspect of the priorities that led
to me revising Kevin's 2003 patch in the first place.

So in my view, dwarf2expr.[ch] should construct a data structure that
accurately reflects the result of evaluating a Dwarf 2 location
expression; it should be a Dwarf-specific data structure.  The
construction of something like a 'struct location' should be left to
dwarf2loc.c.


  reply	other threads:[~2004-08-04 18:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-03  7:15 Jim Blandy
2004-08-04 16:53 ` Andrew Cagney
     [not found]   ` <vt2fz7292z3 dot fsf at zenia dot home>
     [not found]     ` <41112BAE dot 9080304 at gnu dot org>
     [not found]       ` <vt2hdri4mi1 dot fsf at zenia dot home>
     [not found]         ` <41115B4F dot 1080700 at gnu dot org>
     [not found]           ` <vt2pt66zgul dot fsf at zenia dot home>
2004-08-04 18:26   ` Jim Blandy [this message]
2004-08-04 18:32     ` Andrew Cagney
2004-08-04 21:35       ` Jim Blandy
2004-08-04 21:55         ` Andrew Cagney
2004-08-04 22:22           ` Jim Blandy
2004-08-04 23:04             ` Daniel Jacobowitz
2004-08-04 23:17               ` Jim Blandy
2004-08-05  9:54                 ` Mark Kettenis
2004-08-05 14:31                   ` Jim Blandy
2004-08-05 16:27                     ` Joel Brobecker
2004-08-05 18:45                       ` Jim Blandy
2004-08-05 18:47                         ` Daniel Jacobowitz
2004-08-05 19:56                           ` Andrew Cagney
2004-08-05 20:36                             ` Daniel Jacobowitz
2004-08-05 20:50                               ` Andrew Cagney
2004-08-06  9:39                     ` Eli Zaretskii
2004-08-10 19:55                       ` Jim Blandy
2004-08-11 20:31                         ` Jim Blandy
2004-08-11 20:33                           ` Daniel Jacobowitz

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=vt2fz7292z3.fsf@zenia.home \
    --to=jimb@redhat.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