Linked by Nicholas Blachford on Wed 9th Jul 2003 16:43 UTC
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
More News »
Sponsored Links



As Nicholas pointed out in this article CISC-commands are hard to decode, they are more complex, have different length ... But this also means that a CISC command carries more information from the memory to the processor than a RISC command. Nicholas also stated that the bottleneck is the processor <-> memory connection. So you can regard CISC commandos as a kind of compression algorithm, so more information can be transported to the CPU, which has time to decode this information into something it can handle optimal.
I can't provide you a link, but IBM thinks about integrating a GZIP-unit at memory controller and at processor for its zSeries, so the data are compressed before transfer.
Anton