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.

Politics : Formerly About Advanced Micro Devices -- Ignore unavailable to you. Want to Upgrade?

To: Goutam who wrote (74984)	10/11/1999 12:06:00 PM
From: Haim Barad	Read Replies (2) \| Respond to of 1575955

As I responded in a different post on the Intel thread, the fact that the Athelon has a prefetch with the same opcode won't help in most applications. Most applications will query for processor type and use a processor specific code (if desired). An SSE optimized codebase would fail on an Athelon if it contained unrecognized opcodes. They would have to create a 3DNOW codebase for K6-2/3 and an "enhanced 3DNOW" codebase for the Athelon and then run the proper one. Now if AMD didn't diverge in the past and went with SSE (i.e. stayed 100% compatible with Intel), then all Intel optimized code would help all AMD chips. This is no longer true. Haim