Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| Reasons why you don't prove your programs are correct steve@hubcap.clemson.edu (1990-01-05) |
| Re: Reasons why you don't prove your programs are correct keithd@anvil.oz.au (1990-01-12) |
| Re: Reasons why you don't prove your programs are correct mayer@iuvax.cs.indiana.edu (Mayer Goldberg) (1990-01-17) |
| Re: Reasons why you don't prove your programs are correct pardo@cs.washington.edu (1990-01-22) |
| Re: Reasons why you don't prove your programs are correct pardo@cs.washington.edu (1990-01-24) |
| Re: Reasons why you don't prove your programs are correct gateley@m2.csc.ti.com (1990-01-26) |
| From: | pardo@cs.washington.edu (David Keppel) |
| Newsgroups: | comp.compilers |
| Date: | 24 Jan 90 02:51:52 GMT |
| References: | <7578@hubcap.clemson.edu> <1990Jan16.232703.2368@esegue.segue.boston.ma.us> <1990Jan22.234119.7002@esegue.segue.boston.ma.us> |
| Organization: | University of Washington, Computer Science, Seattle |
>>[Why don't you prove your programs correct?]
One of the guys here says that the i386 is a favorite of the
high-reliability guys. They have to ``prove'' the correctness of
their programs. They want as CISC a machine as possible, so they
have less to do. They take it as granted that the underlying
hardware works correctly!
A related issue: do you prove your compiler correct?
;-D on ( The proof is in the pudding!? ) Pardo
--
pardo@cs.washington.edu
{rutgers,cornell,ucsd,ubc-cs,tektronix}!uw-beaver!june!pardo
Return to the
comp.compilers page.
Search the
comp.compilers archives again.