Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!snorkelwacker!spdcc!esegue!compilers-sender
From: MERRIMAN@ccavax.camb.com (George Merriman -- CCA/NY)
Newsgroups: comp.compilers
Subject: Re: Unsafe Optimizations (WAS: Compiler Design in C How about it?)
Message-ID: <25600.266a8927@ccavax.camb.com>
Date: 5 Jun 90 02:51:56 GMT
References: <1990Jun1.194941.5781@esegue.segue.boston.ma.us> <1990Jun4.044255.14857@esegue.segue.boston.ma.us>
Sender: compilers-sender@esegue.segue.boston.ma.us
Reply-To: George Merriman -- CCA/NY <MERRIMAN@ccavax.camb.com>
Organization: Cambridge Computer Associates, Inc.
Lines: 19
Approved: compilers@esegue.segue.boston.ma.us
News-Moderator: Approval required for posting to comp.compilers

In article <1990Jun4.044255.14857@esegue.segue.boston.ma.us>, pardo@cs.washington.edu (David Keppel) writes:

>  Anyway, at this point one of my
> classmates -- who has worked on optimizing compilers for several
> high-performance computers -- tells me that I am free to feel that way,
> but that her customers won't buy my product.  They'd rather spend time
> figuring out why their code gives wrong answers than spend time waiting
> for their computer to give the right answer.  (Ok, so they run programs
> that take a week to execute...)

But can these people (and others who may inherit the code) always tell a wrong
answer when they see one?

George Merriman, Cambridge Computer Associates

-- 
Send compilers articles to compilers@esegue.segue.boston.ma.us
{spdcc | ima | lotus}!esegue.  Meta-mail to compilers-request@esegue.
Please send responses to the author of the message, not the poster.