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 210.24-1.9%10:48 AM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: g_w_north who wrote (68942)1/25/2002 6:44:34 PM
From: TGPTNDR of 275872
 
GW, Re: <...but I do know that MMX, SSE etc. don't interfere with the basic underlying architecture of the overall chip. If 3DNow! or some form of SSE is present on the chip this will allow certain applications to take advantage of those instruction sets. They will not interfere compatibility wise. Somebody correct me if I'm wrong....>

What you're saying is correct. what you're missing is that someone has to code for the underlying architecture and various options of code sets.(Could be the application coder, could be the compiler coder. Most likely the application coder.)

What that amounts to is that there are applications out there that stipulate they work on P-III or better. That statement generally means they use 3Dnow! and/or SSE instructions.

In each generation of software design the managers/coders are trying to maximize the utility and sale ability of their products.

If AMD gets there first and gets a good base Intel pretty much has to provide some kind of compatibility. They are certainly free to not provide the compatibility(In which case some software won't run as well -- if at all -- on their machines), and they can also provide extensions not in the AMD product.

The point is that nobody is likely to code(or compile) software in the near future that'll preclude execution on the Athlon/P-III product lines(Cause that's the embedded base where the profit is). That's the only place compatibility comes from.

As long as you don't break old stuff you can add whatever you want.

But the software keeps getting more expensive as the old *CRAP* gets dragged along. Eventually, the software developers decide there's no reason to include code for the old instructions and it goes away.

Intel's said it's time to make the break. Amd's said it'll live with the leavings for a while. Intel seems to have said, OK, pass the Mustard, we'll eat old stuff with you for a while. It had to happen. Both Intel and AMD knew it would.

No big deal.

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