From: "karthikeyan natarajan" <karthik_96cse@yahoo.com>
To: Michael Uhler <uhler@mips.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Regarding branch delay instructions in R4000
Date: Sat, 20 Dec 2003 09:53:12 +0000 (GMT) [thread overview]
Message-ID: <20031220095312.38822.qmail@web10104.mail.yahoo.com> (raw)
In-Reply-To: <1071816092.30316.8.camel@gmu-linux>
Hi gmu,
Have got a one more doubt...
MIPS stands for Microprocessor without Interlocked
Pipeline Stages.
But, in the "R4400_Uman_book_Ed2.pdf" doc, it is
mentioned that the CPU general registers are
interlocked. I am bit confused after reading this doc.
Would be great if you clarify this doubt too...
Thanks much,
-karthi
> The MIPS architecture specifies a single delay slot
> after a branch
> or jump. The fact that the R4000 implementation
> (and pretty much
> any of the ones following) had a pipeline in which
> more instructions
> had already entered the pipe before the branch is
> resolved is not
> relevant to the architecture specification. In the
> case you
> mention, a single instruction is executed after the
> branch, as
> architecturally required, and any subsequent
> instructions in the
> pipe are killed.
>
> /gmu
>
> On Thu, 2003-12-18 at 22:01, karthikeyan natarajan
> wrote:
> > Hi All,
> >
> > If this is not a right forum to ask this
> Question,
> >
> > please redirect me to the appropriate one...
> > Since R4000 is using the 8 stage pipeline,
> three
> > instructions are already entered into the pipeline
> > when the branch instruction is executed. Out of
> these
> > three instructions, the first instruction will be
> > executed for sure.
> >
> > My question is:
> > What happens to the other two instruction that
> are
> > in the delay slots? are they nullified?
> > Could anyone please shed some light on this.
> >
> > Thanks much,
> > -karthi
> >
> > =====
> > The expert at anything was once a beginner
> >
> >
>
________________________________________________________________________
> > Yahoo! Messenger - Communicate instantly..."Ping"
> > your friends today! Download Messenger Now
> > http://uk.messenger.yahoo.com/download/index.html
> >
> --
> Michael Uhler, Chief Technology Officer
> MIPS Technologies, Inc. Email: uhler@mips.com
> Pager: uhler_p@mips.com
> 1225 Charleston Road Voice: (650)567-5025 FAX:
> (650)567-5225
> Mountain View, CA 94043 Mobile: (650)868-6870
> Admin: (650)567-5085
>
>
=====
The expert at anything was once a beginner
________________________________________________________________________
Yahoo! Messenger - Communicate instantly..."Ping"
your friends today! Download Messenger Now
http://uk.messenger.yahoo.com/download/index.html
next prev parent reply other threads:[~2003-12-20 9:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-19 6:01 Regarding branch delay instructions in R4000 karthikeyan natarajan
2003-12-19 6:41 ` Michael Uhler
2003-12-20 9:53 ` karthikeyan natarajan [this message]
2003-12-20 10:16 ` Kevin D. Kissell
2003-12-20 10:16 ` Kevin D. Kissell
2003-12-22 12:47 ` Maciej W. Rozycki
2004-01-04 9:09 ` Regarding the LL & SC instructions karthikeyan natarajan
2004-01-04 21:47 ` Kevin D. Kissell
2004-01-04 21:47 ` Kevin D. Kissell
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=20031220095312.38822.qmail@web10104.mail.yahoo.com \
--to=karthik_96cse@yahoo.com \
--cc=linux-mips@linux-mips.org \
--cc=uhler@mips.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