Silicon Investor (SI) -- The First Internet Community

STOCKTALK

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) -- Ignore unavailable to you. Want to Upgrade?

To: wanna_bmw who wrote (62232)	11/5/2001 2:10:54 PM
From: Tenchusatsu	Respond to of 275872

BMW, I'm sure Kap knows the truth, but he's either purposely spreading FUD, or he's trying to get underneath your skin. I'm seeing a lot of that these days from both sides of the fence. Count me out. Tenchusatsu

To: wanna_bmw who wrote (62232)	11/5/2001 2:22:43 PM
From: Joe NYC	Read Replies (1) \| Respond to 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

To: wanna_bmw who wrote (62232)	11/5/2001 2:35:47 PM
From: kapkan4u	Read Replies (1) \| Respond to of 275872

<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. You can have your own guess as to how fast it really is, but arguing over it, like I said, is irrelevant.> Now that you asked around and found out the truth, you say its irrelevant. Before you said that I was spreading FUD. Ofcource the trace cache helps to minimize the impact of the half clocked decode. That was the whole idea behind the TC - keep the decode logic largely unchanged from the good old P6, but make the rest of the Willy downstream run twice as fast. Kap