From: "Nathan J. Williams" <nathanw@wasabisystems.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: Modernize NetBSD/powerpc support in GDB
Date: Fri, 12 May 2006 21:37:00 -0000 [thread overview]
Message-ID: <mtu3bffvsfs.fsf@contents-vnder-pressvre.mit.edu> (raw)
In-Reply-To: <200605122048.k4CKmqjQ020427@elgar.sibelius.xs4all.nl>
Mark Kettenis <mark.kettenis@xs4all.nl> writes:
> My bet is still that it is a cache flushing issue, especially since
> the 440, which uses different code to flush the cache, is so much
> better.
Yeah. I've actually figured out what the problem is now, but I don't
yet have a handle on the right fix. This has probably gotten off-topic
for gdb-patches, though; I'll let you know when I get it fixed for
real.
- Nathan
next prev parent reply other threads:[~2006-05-12 21:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 19:44 Mark Kettenis
2006-05-02 20:07 ` Daniel Jacobowitz
2006-05-02 20:23 ` Daniel Jacobowitz
2006-05-12 1:55 ` Nathan J. Williams
2006-05-12 21:34 ` Mark Kettenis
2006-05-12 21:37 ` Nathan J. Williams [this message]
2006-05-12 21:55 ` Nathan J. Williams
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=mtu3bffvsfs.fsf@contents-vnder-pressvre.mit.edu \
--to=nathanw@wasabisystems.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