From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@red-bean.com>
Cc: gdb@sourceware.org
Subject: Re: Prologue analysis interface
Date: Tue, 22 Nov 2005 19:44:00 -0000 [thread overview]
Message-ID: <20051122193034.GA25326@nevyn.them.org> (raw)
In-Reply-To: <8f2776cb0511221124u988f759u17418a114e1f3b7c@mail.gmail.com>
On Tue, Nov 22, 2005 at 11:24:06AM -0800, Jim Blandy wrote:
> Daniel, you said that you felt that the interface in the
> prologue-value.h that I posted wasn't at the right level, and
> suggested that, instead of providing types and some operations on
> those types, it should instead provide the interpretation loop and
> call back into tdep code to interpret specific instructions.
>
> Could you sketch that interface for me? I'm concerned that it will be
> difficult to allow the tdep code the flexibility it needs to model the
> processor without a lot of bureaucracy, but I'm willing to be
> impressed.
What I don't know is how much flexibility is needed. Maybe it's more
than I thought.
I'm penciling in reading the existing s390 analyzer and posted m32c
analyzers for tonight's schedule, since this keeps coming up in
conversation. I promise I'll get back to you about this soon.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-11-22 19:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 19:30 Jim Blandy
2005-11-22 19:44 ` Daniel Jacobowitz [this message]
2005-11-23 0:20 ` Jim Blandy
2005-11-23 2:14 ` Daniel Jacobowitz
2005-11-23 2:52 ` Joel Brobecker
2005-11-23 3:52 ` Jim Blandy
2005-11-23 16:56 ` Ulrich Weigand
2005-11-23 18:37 ` Joel Brobecker
2005-11-24 6:21 ` Jim Blandy
2005-11-24 10:21 ` Jim Blandy
2005-11-24 17:18 ` Ulrich Weigand
2005-11-25 3:06 ` Jim Blandy
2005-11-23 3:14 ` Jim Blandy
2005-11-23 6:18 ` Daniel Jacobowitz
2005-11-23 14:54 ` Ulrich Weigand
2006-01-27 17:11 ` Daniel Jacobowitz
2006-01-27 18:25 ` Jim Blandy
2006-01-28 13:40 ` Jim Blandy
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=20051122193034.GA25326@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=jimb@red-bean.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