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: Petz who wrote (25809)	11/11/1997 1:16:00 AM
From: Elmer	Respond to of 1579738

Petz, It certainly is a pleasure to see a reasonable response once in a while. I will try to be as reasonable as you have been. We all make mistakes once in a while and I have at times made my own share too. You may be very correct in that the probability of any commercial code causing the K6 to actually demonstrate this bug is very small, but do you think that Intel would get away with that kind of a position? The fact that the media allows these AMD bugs to go unnoticed, however insignificant they may be in real applications, is what strikes me as extremely unfair. If these bugs existed in Intel processors you know as well as do I that CNN would be doing a special on "Intel's ongoing problem", if they aren't already doing one. That's what bugs me. Having said that, I also can't understand why Intel doesn't have a room full of geeks doing everything they can possibly think of to crash Intel systems. What's a couple of million and a few cans of jolt to Intel to head off these problems? This is stupid and Intel deserves criticism for it. I would just like to point out that AMD is no virgin either. They have their own bugs too, they just don't have the spotlight. EP