From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org, fnf@specifix.com
Subject: Re: Fix PR breakpoints/2080
Date: Tue, 14 Feb 2006 16:59:00 -0000 [thread overview]
Message-ID: <20060214165903.GA26163@nevyn.them.org> (raw)
In-Reply-To: <200602141638.k1EGckea012314@elgar.sibelius.xs4all.nl>
On Tue, Feb 14, 2006 at 05:38:46PM +0100, Mark Kettenis wrote:
> > X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on
Hmm, your mailer likes inserting blank lines in headers sometimes.
Odd.
> > Of course in optimized code we don't expect the prologue skipper to
> > work very well, and we use dwarf2 to bypass the prologue analyzer,
> > so this may not be a big deal. But I'm somewhat curious to see if
> > we could make this extremely sophisticated i386 prologue analyzer
> > use Jim's prologue-value.[ch] interface...
>
> Well, writing that prologue analyzer will be hell of a lot more
> difficult for CISC than it is for RISC; even with Jim's
> prologue-value.[ch].
Totally true.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-02-14 16:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 15:45 Mark Kettenis
2006-02-14 15:52 ` Daniel Jacobowitz
2006-02-14 16:39 ` Mark Kettenis
2006-02-14 16:59 ` Daniel Jacobowitz [this message]
2006-02-14 20:23 ` Jim Blandy
2006-02-20 13:58 ` Fred Fish
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=20060214165903.GA26163@nevyn.them.org \
--to=drow@false.org \
--cc=fnf@specifix.com \
--cc=gdb-patches@sourceware.org \
--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