From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: "David S. Miller" <davem@davemloft.net>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH]: Setup sparc32 to support dwarf2 unwind sniffer
Date: Wed, 05 Apr 2006 13:38:00 -0000 [thread overview]
Message-ID: <20060405133837.GA29408@nevyn.them.org> (raw)
In-Reply-To: <11768.192.87.1.22.1144228265.squirrel@webmail.xs4all.nl>
On Wed, Apr 05, 2006 at 11:11:05AM +0200, Mark Kettenis wrote:
> Perhaps we should try to address those issues. I never went through the
> trouble of making the sparc and sparc64 prologue analyzers any smarter,
> because I never encountered any code that made it fail.
If you want to make the analyzer smarter, which would be nice, may I
recommend trying Jim's now-committed prologue-value.h interface?
I'll get around to posting the rewritten Thumb analyzer soon, I hope.
It was remarkably easy to write, and works better too.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-04-05 13:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-05 3:30 David S. Miller
2006-04-05 9:11 ` Mark Kettenis
2006-04-05 13:38 ` Daniel Jacobowitz [this message]
2006-04-05 18:54 ` David S. Miller
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=20060405133837.GA29408@nevyn.them.org \
--to=drow@false.org \
--cc=davem@davemloft.net \
--cc=gdb-patches@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
/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