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 : Intel Corporation (INTC)
INTC 45.51+10.7%Jan 9 9:30 AM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Tony Viola who wrote (39989)11/11/1997 12:54:00 PM
From: Petz  Read Replies (1) of 186894
 
Tony, RE: Bugs like this are found in mission critical system 390 and other large scale computers to which companies like Ford, Daimler Benz, AT&T, EDS, and other multi-billion dollar companies commit their entire operations

They are NOT. The IBM 360 series and its followons had a much more regular instruction set where the opcode is completely defined in the first byte. This is totally unlike the x86 architecture which has grown out of control with bits all over the place defining new instructions for each new generation.

The problems are fixed almost always by microcode patches.

If such a bug were found on a mainframe, you are right, the microcode would be patched by replacing a PROM. On an Intel CPU this is totally impossible -- the microcode is embedded in the silicon. A software patch to scan for the 4-byte sequence is also totally inadequate because any hacker could write a program to generate the code one microsecond before executing it.

Intel's only recourse is a recall.

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