Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!danews!lvc
From: lvc@danews.UUCP
Newsgroups: comp.arch,comp.lang.c
Subject: Optimization vs. the programmer
Message-ID: <479@danews.ATT.COM>
Date: Mon, 6-Apr-87 21:57:09 EST
Article-I.D.: danews.479
Posted: Mon Apr  6 21:57:09 1987
Date-Received: Wed, 8-Apr-87 06:00:16 EST
Organization: AT&T Medical Information Systems, Columbus, Oh
Lines: 22
Xref: utgpu comp.arch:789 comp.lang.c:1488

I'm all for optimization but ...

There is a certain computer (that I still use) that
requires the statement:

	n = n;

in order to force the hardware to work right for certain
values of n.  Well fix the **** computer you say, and
so do I.  But that will be a while and I can't wait.

If I had an optimizing compiler that was smart (?$!?)
enough to excise this I couldn't make the machine work
right.

Please dear compiler writers, make the compiler do what I
tell it (or at least have the courtesy to warn me about it).
If hardware was perfect then I wouldn't have a gripe, but
it ain't so I do.
-- 

	Larry Cipriani, AT&T Network Systems, Columbus OH, (614) 860-4999