Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: nathanw@wasabisystems.com
Cc: gdb-patches@sourceware.org
Subject: Re: Modernize NetBSD/powerpc support in GDB
Date: Fri, 12 May 2006 21:34:00 -0000	[thread overview]
Message-ID: <200605122048.k4CKmqjQ020427@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <mtuslnghurv.fsf@contents-vnder-pressvre.mit.edu> 	(nathanw@wasabisystems.com)

> From: "Nathan J. Williams" <nathanw@wasabisystems.com>
> Date: 11 May 2006 21:55:00 -0400
> 
> This seems good, though less dramatic than you report. On my macppc
> system, it took the testsuite from 788 to 753 failures (though with a
> notable number of PASS->FAIL changes as well)

I had some PASS->FAIL changes as well; I looked at a few of them but
they all seemed to be related to GDB missing a breakpoint.  Presumably
these breakpoints are now missed because an earlier test now PASSes
and the instruction cache is in a somewhat different state now.

> ; on a AMCC 440 system, it went from 179 to 170 failures, with only
> one PASS->FAIL regression (which is a mysterious additional ^M in
> the output of "info all-registers".

Thanks for testing; I'm committing the diff then ;-).  I've seen
spurious ^M's in the "info all-registers" output on OpenBSD/sparc and
OpenBSD/sparc64 as well.

> Summary diffs attached, and I'm trying to figure out
> why macppc is so much worse than the 440.

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.


  reply	other threads:[~2006-05-12 20:48 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 [this message]
2006-05-12 21:37     ` Nathan J. Williams
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=200605122048.k4CKmqjQ020427@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=gdb-patches@sourceware.org \
    --cc=nathanw@wasabisystems.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