Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!nike!ucbcad!ucbvax!hplabs!tektronix!uw-beaver!uw-june!bnfb
From: bnfb@uw-june (Benson)
Newsgroups: net.lang.c
Subject: Optimizing C compilers, and their use...
Message-ID: <1184@uw-june>
Date: Mon, 1-Sep-86 18:13:03 EDT
Article-I.D.: uw-june.1184
Posted: Mon Sep  1 18:13:03 1986
Date-Received: Tue, 2-Sep-86 20:47:33 EDT
Organization: U of Washington Computer Science
Lines: 18
Keywords: optimize, C, compiler

All the time, on the net, in casual conversation, in literature and
especially in discussions of the forthcoming C Language Standard, I have
heard the statement:
	"You can allow/do/write <anything> because any
	 decent optimizing compiler will fix/compile it."
My question is:
	How many of you who say this (or even just how many of you
	on the net) have an optimizing C compiler?  And how many of
	those actually use them?
Until people have them, work-arounds ("kludges") will have to be.  And
until people use the compilers, just writing <anything> won't do.

						Bjorn Freeman-Benson

P.S. Oh, and what would you be willing to pay (up-and-above normal
C compiler costs) for such an optimizing compiler?  Remember - until
you have one, you can't take advantage of it, but them engineers who
wrote it have a done a lot of work...