From: Ralf Baechle <ralf@oss.sgi.com>
To: Harald Koerfgen <Harald.Koerfgen@home.ivm.de>
Cc: linux-mips@oss.sgi.com
Subject: Re: MIPS32 patches breaking DecStation
Date: Tue, 9 Jan 2001 16:28:35 -0200 [thread overview]
Message-ID: <20010109162835.B4232@bacchus.dhis.org> (raw)
In-Reply-To: <XFMail.010109181100.Harald.Koerfgen@home.ivm.de>; from Harald.Koerfgen@home.ivm.de on Tue, Jan 09, 2001 at 06:11:00PM +0100
On Tue, Jan 09, 2001 at 06:11:00PM +0100, Harald Koerfgen wrote:
> > No problem - Done - doesnt work
>
> Same here on my /260 (R4400SC V4.0). Neither inserting four "sll $0,$0,1" nor
> four "nop" seem to work. The branch, on the other hand, does.
Note the ssnops only make sense on superscalar CPUs, so not on the R4000.
Also note that the branch is equivalent to three nops. One for the
branch instruction itself, the two more for instructions in the pipeline
that get killed. On the R4600 / R500 where the hazard is only a single
instruction the branch is equivalent to only a single nop. So while
unobvious the branch is a rather neat idea.
Ralf
next prev parent reply other threads:[~2001-01-09 18:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 23:41 MIPS32 patches breaking DecStation Florian Lohoff
2001-01-08 23:41 ` Florian Lohoff
2001-01-09 0:34 ` Kevin D. Kissell
2001-01-09 0:34 ` Kevin D. Kissell
2001-01-09 8:54 ` Florian Lohoff
2001-01-09 17:11 ` Harald Koerfgen
2001-01-09 18:28 ` Ralf Baechle [this message]
2001-01-09 19:30 ` Kevin D. Kissell
2001-01-09 19:30 ` Kevin D. Kissell
2001-01-09 19:54 ` Ralf Baechle
2001-01-09 19:54 ` Ralf Baechle
2001-01-09 20:33 ` Kevin D. Kissell
2001-01-09 20:33 ` Kevin D. Kissell
2001-01-09 15:09 ` Ralf Baechle
2001-01-09 15:09 ` Ralf Baechle
2001-01-09 15:50 ` Kevin D. Kissell
2001-01-09 15:50 ` Kevin D. Kissell
2001-01-09 16:43 ` Harald Koerfgen
2001-01-09 17:01 ` Ralf Baechle
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=20010109162835.B4232@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=Harald.Koerfgen@home.ivm.de \
--cc=linux-mips@oss.sgi.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