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 : Advanced Micro Devices - Moderated (AMD)
AMD 214.90-0.1%Dec 26 3:59 PM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: wanna_bmw who wrote (62232)11/5/2001 2:22:43 PM
From: Joe NYCRead Replies (1) of 275872
 
wbmw,

Now, the decode logic has its own pipeline that is running independently of the main pipeline. You may be right about the clock being slower, but the fact is that Intel has never specified.

There is an answer to this. The decode stage either runs at the speed of main clock or it does not. This fact is independent of whether Intel specified or disclosed it.

The Pentium 4 only needs to decode instructions 1/5 of the time, and really tight program loops can obviously make this ever smaller. That's why optimizing code is so important.

I think you may be going overboard with this a bit. How can you possibly optimize your program for the size of the trace cache?

And you have no control what's in the trace cache, since there may be other apps running in the background, the more apps, more trace cache trashing there has to be (at the full decoder delay - whatever it is).

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