home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.arch
- Path: sparky!uunet!ferkel.ucsb.edu!taco!gatech!darwin.sura.net!zaphod.mps.ohio-state.edu!sdd.hp.com!ux1.cso.uiuc.edu!csrd.uiuc.edu!sp90.csrd.uiuc.edu!grout
- From: grout@sp90.csrd.uiuc.edu (John R. Grout)
- Subject: Re: RISC goes CISC?
- Message-ID: <1992Nov9.193615.6513@csrd.uiuc.edu>
- Sender: news@csrd.uiuc.edu
- Reply-To: j-grout@uiuc.edu
- Organization: UIUC Center for Supercomputing Research and Development
- References: <1992Nov6.092012.19239@rhein-main.de> <1992Nov8.193946.2210@cs.mcgill.ca>
- Date: Mon, 9 Nov 92 19:36:15 GMT
- Lines: 17
-
- storm@cs.mcgill.ca (Marc WANDSCHNEIDER) writes:
-
- > Given current technologies, it could end up being EXTREMELY difficult
- >to make instructions execute in one clock cycle, if the clock cycles starting
- >dropping below a certain time. There is just so much that goes on, and gates
- >can only go so fast. Thus, the compromize is to try and overlap execution.
-
- Note that this can be done either through superscalar (multiple
- execution units/pipelines) or superpipelining (very short cycle time
- with multiple pipeline stages for things like decode and execute)
- techniques or both (e.g., the DEC 21064 has a very fast cycle time and
- two parallel execution pipelines for integer and floating-point
- operations).
- --
- John R. Grout j-grout@uiuc.edu
- University of Illinois, Urbana-Champaign
- Center for Supercomputing Research and Development
-