From: Daniel Jacobowitz <drow@mvista.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Limited DW_OP_piece support
Date: Thu, 22 May 2003 18:19:00 -0000 [thread overview]
Message-ID: <20030522181932.GA31074@nevyn.them.org> (raw)
In-Reply-To: <1030522170039.ZM30271@localhost.localdomain>
On Thu, May 22, 2003 at 10:00:39AM -0700, Kevin Buettner wrote:
> The patch below adds limited DW_OP_piece support to dwarf2expr.c. I
> will post a patch to rs6000-tdep.c which illustrates what a
> ``dwarf2_compose_register_pieces'' method should look like.
>
> Okay?
I would really strongly prefer that we not do it this way.
You'll notice that there are no other gdbarch calls in the expression
evaluator. There might be some implicit ones through macros, for
instance there is TARGET_ADDR_BIT. That needs to be fixed properly
some day already.
Instead, IMHO, we should devise a way to represent multiple locations
in the evaluator's return value. This is not suggesting the complete
overhaul that we need to support multiple locations in the rest of GDB.
Then have the expression evaluator properly return a list of locations,
and have the massaging done via gdbarch in the evaluator's client.
Does that sound reasonable?
Maybe a flag to the evaluator which says whether we're looking for a
location, for better sanity checking. Not sure about that part.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-05-22 18:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-22 17:00 Kevin Buettner
2003-05-22 17:53 ` Andrew Cagney
2003-05-22 18:30 ` Kevin Buettner
2003-05-22 18:42 ` Andrew Cagney
2003-05-22 18:19 ` Daniel Jacobowitz [this message]
2003-05-22 21:21 ` Kevin Buettner
2003-05-22 21:29 ` Daniel Jacobowitz
2003-05-22 21:42 ` Kevin Buettner
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=20030522181932.GA31074@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@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