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: Sun, 09 Oct 2005 20:27:00 -0000 [thread overview]
Message-ID: <20051009202726.GE7107@nevyn.them.org> (raw)
In-Reply-To: <m3y8568as0.fsf@alligator.red-bean.com>
On Thu, Oct 06, 2005 at 04:51:11PM -0700, Jim Blandy wrote:
> If folks are interested, I can post the m32c prologue analyzer that
> uses these functions, as an example of how they can be used.
>
> 2005-10-06 Jim Blandy <jimb@redhat.com>
>
> * prologue-value.c, prologue-value.h: New files.
> * Makefile.in (prologue_value_h): New variable.
> (HFILES_NO_SRCDIR): List prologue-value.h.
> (ALLDEPFILES): List prologue-value.c.
> (prologue-value.o): New rule.
I like the idea.
I'd love to see the m32c example. The arithmetic is easy to grasp, but
the choices you made for memory (and the special-case for array
references) are a lot less obvious without some more context.
I have a half-baked feeling that the exported interface is at a bad
level of abstraction, i.e. that too much generic code will end up
crammed into the tdep files. But I don't have any evidence to back
that up.
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.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-10-09 20:27 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 [this message]
2005-10-13 0:20 ` Jim Blandy
2005-10-13 1:04 ` Daniel Jacobowitz
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=20051009202726.GE7107@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