On 3/19/07, Karel Kulhavy <[EMAIL PROTECTED]> wrote:
On Mon, Mar 19, 2007 at 07:23:43AM -0700, Darrin Chandler wrote:
> But if you write a program and the user finds it full of bugs, are they > going to care that you can say that it's GCC's fault? The burden falls > on the developers to make code that works, including working around > problems in the compiler. Sad, but true. We can analogically use this argument for ocassional errors in memory, too. If I write a program and the user finds it crashing all the time, are they going to care that you can say that their hardware may be unstable?
Yeah but see, you can try it on different hardware and show that it works. GCC is the only option for compiling we've got, so your analogy fails.
OpenBSD then should be written with Hamming, Golay, or Reed-Solomon codes in all the internal structures, to automatically recover from flipped bits in data structures. Similar protection should be done to the code. The code should be periodically CRC-ed and the process image snapshotted. If it were revealed the code is corrupted, a rollback would be done and the process restarted.
What do you want?? You must be being sarcastic in some of these posts but I can't tell which. -Nick
