Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: Jim Blandy <jimb@redhat.com>, Joel Brobecker <brobecker@gnat.com>,
	Mark Kettenis <kettenis@jive.nl>,
	gdb@sources.redhat.com
Subject: Re: interface to partial support for DW_OP_piece in dwarf2expr.[ch]
Date: Thu, 05 Aug 2004 20:50:00 -0000	[thread overview]
Message-ID: <41129D74.8030609@gnu.org> (raw)
In-Reply-To: <20040805203421.GA17540@nevyn.them.org>

> On Thu, Aug 05, 2004 at 03:55:50PM -0400, Andrew Cagney wrote:
> 
>>>> >On Thu, Aug 05, 2004 at 01:42:25PM -0500, Jim Blandy wrote:
>>>> >
>>>
>>>>>> >>>
>>>>>> >>>Without stopping discussion of the best way to handle scattered values
>>>>>> >>>in core GDB, I'd still like to hear comments on my suggested change to
>>>>>> >>>dwarf2expr.[ch]'s interface, if there are any.
>>>>>> >>>
>>>>>> >>>Because dwarf2expr is supposed to be concerned with evaluating Dwarf
>>>>>> >>>expressions, and *avoid* building GDB data structures directly, I
>>>>>> >>>think that change can be assessed separately from the larger (and
>>>>>> >>>harder, and more important) question.
>>>
>>>> >
>>>> >
>>>> >I think it's fine.  You spelled "yield" wrong.
>>
>>> 
>>> Did this get answered?
>>
>>>> >- a single value can have multiple locations (important for store)
> 
> 
> No.

I was worried I'd missed something.

> dwarf2loc, which deals with the lists of
> locations, will need to be aware of this; but a single location
> expression only has one location.

ah, thank you.

Andrew



  reply	other threads:[~2004-08-05 20:50 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
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 [this message]
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=41129D74.8030609@gnu.org \
    --to=cagney@gnu.org \
    --cc=brobecker@gnat.com \
    --cc=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@redhat.com \
    --cc=kettenis@jive.nl \
    /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