From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>, gdb-patches@sources.redhat.com
Cc: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
Subject: Re: [RFA] mips32_next_pc overdue cleanup
Date: Thu, 05 Jul 2001 13:29:00 -0000 [thread overview]
Message-ID: <3B44CE13.8070405@cygnus.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1010705094609.15332F-100000@is>
Eli wrote:
> According to the masks in the opcodes
>> directory, these changes are rigt, and what we had before can't possibly
>> work. Especially the fact that we would never, ever predict a BNE as taken
>> before these changes convinced me that they really were correct and this
>> code had never been particularly tested. Comments?
>
>
> I'd appreciate a short test case for this. I'd like to verify that
> the previous stuff indeed didn't work and that the new stuff does.
>
> Assuming that this code is run on SGI Irix, that is.
I'm wondering the same thing.
> I'll try to make one. I'm not immediately sure how.
>
> It looks almost as if this code was for an unreleased port inside
> Cygnus - anyone know if that's true? I see active work on it in 1998
> and 2000 in the ChangeLogs, and no mention of removing calls to it
> - but nothing uses it at all.
I'll do some digging.
One thing, it is very easy for a software single step function to be
implemented yet never tested - everything supports h/w singlestep
now-a-days.
Andrew
next prev parent reply other threads:[~2001-07-05 13:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-04 11:41 Daniel Jacobowitz
2001-07-04 23:45 ` Eli Zaretskii
2001-07-05 0:00 ` Daniel Jacobowitz
2001-07-05 13:29 ` Andrew Cagney [this message]
2001-07-05 13:34 ` Daniel Jacobowitz
2001-07-05 13:51 ` Andrew Cagney
2001-07-05 14:05 ` Stan Shebs
[not found] ` <3B454B1B.7040506@cygnus.com>
2001-07-05 22:37 ` Daniel Jacobowitz
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=3B44CE13.8070405@cygnus.com \
--to=ac131313@cygnus.com \
--cc=dmj+@andrew.cmu.edu \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.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