SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Intel Corporation (INTC)
INTC 34.32-1.2%Nov 18 3:59 PM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Scumbria who wrote (107894)8/21/2000 1:55:54 PM
From: Tenchusatsu  Read Replies (2) of 186894
 
Scumbria, <I'm questioning how many bubbles it will remove. That is what determines it value to performance.>

I think you're looking at the wrong thing. The pipeline bubbles will be there no matter what, and increasing the width or the speed of the integer execution unit isn't going to do a thing about those bubbles.

But if you have a loop of code that will be iterated many, many times, the pipeline bubbles will be reduced down to a minimum. Then performance is limited by how many clock cycles it will take to execute the instructions per iteration. And the more instructions you can squeeze in per clock, the better. Of course, the squeezing will be limited by hazards, especially data dependencies. But since Willamette's double-speed ALU can remove some data hazards, its integer unit will be able to execute more instructions per clock (on average) than a traditional 4-issue integer unit.

Tenchusatsu
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext