Path: utzoo!attcan!uunet!world!decwrl!infopiz!lupine!rfg
From: rfg@NCD.COM (Ron Guilmette)
Newsgroups: comp.sys.intel
Subject: Re: Intel bugs / bugged by Intel :-(
Message-ID: <2290@lupine.NCD.COM>
Date: 27 Oct 90 17:52:56 GMT
References: <JSP.90Oct25155458@glia.u.washington.edu> <13056@encore.Encore.COM>
Organization: Network Computing Devices, Inc., Mt. View, CA
Lines: 30

In article <13056@encore.Encore.COM> jcallen@encore.Com (Jerry Callen) writes:
<>Is this SOP in the industry?  Do Motorola, AMD, NS ...  follow the
<>same policy?
<
<I do know that Motorola and National make this information available
<if you ask for it. Can't say about others.

One champion of us `users' in this regard has been Michael Slater and his
Microprocessor Report.  He has been campaining for full disclosure of
chips bugs for some time now.  He has even managed to extract commitments
from some chip vendors that they will release such information freely,
fully, and in a timely manner (or something like that).

I forget who all the vendors are that he has gotten such commitments from,
but based solely upon the content of the discussion I have been reading
here, I would have to guess that Intel is not among them.

<>Is there a net archive of known bugs?  Any interest in forming one?

I have created and distributed (electronically) lists of bugs in various
C++ language processors, but I am rather straying from the subject now
aren't I?  I just mentioned it so that y'all would know that such things
can be done easily enough, so long as there is one person who is motivated
enough (or paid enough) to maintain and distribute such a bug list.

-- 

// Ron Guilmette  -  C++ Entomologist
// Internet: rfg@ncd.com      uucp: ...uunet!lupine!rfg
// Motto:  If it sticks, force it.  If it breaks, it needed replacing anyway.