From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: general prologue analysis framework
Date: Thu, 13 Oct 2005 01:04:00 -0000 [thread overview]
Message-ID: <20051013010411.GA5540@nevyn.them.org> (raw)
In-Reply-To: <vt27jcis1yo.fsf@theseus.home.>
On Wed, Oct 12, 2005 at 05:19:27PM -0700, Jim Blandy wrote:
> > This all screams out to me that we ought to be able to generate most of
> > the target-specific bits from cgen or somehow reuse existing simulator
> > interfaces. Now that'd be extra credit.
>
> *Exactly*. Machine-independent prologue analysis! If we had a
> machine description in CSDL or something like that, writing the
> prologue analyzer would probably require little more than indicating
> which instructions you wanted to recognize.
That's precisely my point: it's set up the other way round right now.
That calls for an interface in which common code logic calls out to
tdep code to process individual instructions, which is quite the
opposite way round from the target-analyzer-uses-utility-functions
that we've got here.
But I haven't looked at the M32C example yet; I will do that.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-10-13 1:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 20:39 Jim Blandy
2005-10-07 21:25 ` Nathan J. Williams
2005-10-07 21:30 ` Daniel Jacobowitz
2005-10-07 21:41 ` Nathan J. Williams
2005-10-08 7:02 ` Jim Blandy
2005-10-08 7:01 ` Jim Blandy
2005-10-08 16:00 ` Daniel Jacobowitz
2005-10-09 20:27 ` Daniel Jacobowitz
2005-10-13 0:20 ` Jim Blandy
2005-10-13 1:04 ` Daniel Jacobowitz [this message]
2005-10-13 13:50 ` Ulrich Weigand
2005-10-13 17:17 ` Jim Blandy
2005-10-13 17:48 ` Ulrich Weigand
2005-10-13 18:03 ` Daniel Jacobowitz
2005-10-14 18:13 ` Jim Blandy
2005-10-17 18:52 ` Ulrich Weigand
2005-10-17 20:28 ` Jim Blandy
2005-11-23 2:56 ` Ulrich Weigand
2005-10-15 12:12 ` Eli Zaretskii
2005-10-17 20:32 ` Jim Blandy
2005-10-19 8:55 ` Eli Zaretskii
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=20051013010411.GA5540@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=jimb@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