From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: prologue value modules
Date: Thu, 23 Mar 2006 05:24:00 -0000 [thread overview]
Message-ID: <20060323045524.GA31868@nevyn.them.org> (raw)
In-Reply-To: <vt2ek0trd33.fsf@theseus.home.>
On Wed, Mar 22, 2006 at 08:37:20PM -0800, Jim Blandy wrote:
> Okay to commit?
As far as I'm concerned, yes; anyone else have comments on the new
code?
> * 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.
Hmm - why not always build it? It won't get linked in if nothing needs
it, and then ports won't need to mention it in TDEPFILES. And that'll
encourage people to use it I hope :-)
The other port I was using this code for was ARM - I only rewrote the
Thumb analyzer, not the ARM one, but it was simpler and better. Once
this goes in I may try to find some time to do ARM mode too, and submit
it.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-03-23 4:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 5:20 Jim Blandy
2006-03-23 5:24 ` Daniel Jacobowitz [this message]
2006-03-23 5:32 ` Randolph Chung
2006-03-23 5:39 ` Jim Blandy
2006-03-23 14:06 ` Jim Blandy
2006-03-24 1:03 ` Jim Blandy
2006-03-24 2:40 ` Jim Blandy
2006-03-28 7:51 ` Jim Blandy
2006-03-24 14:48 ` Eli Zaretskii
2006-03-24 22:43 ` Jim Blandy
2006-03-28 2:24 ` Jim Blandy
2006-03-28 18:58 ` Eli Zaretskii
2006-03-28 19:15 ` Jim Blandy
2006-03-28 21:17 ` Eli Zaretskii
2006-03-28 21:59 ` Jim Blandy
2006-04-07 19:19 ` Ulrich Weigand
2006-04-08 23: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=20060323045524.GA31868@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@codesourcery.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