Path: utzoo!utgpu!cunews!bnrgate!bigsur!bnr-rsc!bcarh185!schow
From: schow@bcarh185.bnr.ca (Stanley T.H. Chow)
Newsgroups: comp.arch
Subject: Re: speculative execution
Message-ID: <3431@bnr-rsc.UUCP>
Date: 9 Oct 90 21:30:27 GMT
References: <1990Oct9.162639.23516@rice.edu>
Sender: news@bnr-rsc.UUCP
Reply-To: bcarh185!schow@bnr-rsc.UUCP (Stanley T.H. Chow)
Organization: BNR Ottawa, Canada
Lines: 20
Summary:
Followup-To:
Keywords:

In article <1990Oct9.162639.23516@rice.edu> preston@titan.rice.edu (Preston Briggs) writes:
>
>You could probably do it in hardware too (that it, go shooting off
>down some code path before knowing a condition), but I expect
>compilers can do a better job.   Think in terms of trace scheduling.
>-- 
>Preston Briggs				looking for the great leap forward
>preston@titan.rice.edu

Hmm, you mean your compiler can schedule code so that five instructions
are issued to one function unit on every clock?

There are some occasions when multiple copies of h/w can do better than
compiler. I believe speculative execution is one.


Stanley Chow        BitNet:  schow@BNR.CA
BNR		    UUCP:    ..!uunet!bnrgate!bcarh185!schow
(613) 763-2831               ..!psuvax1!BNR.CA.bitnet!schow
Me? Represent other people? Don't make them laugh so hard.