Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!bloom-beacon!spdcc!ima!esegue!compilers-sender
From: jesup@cbmvax.commodore.com (Randell Jesup)
Newsgroups: comp.compilers
Subject: Re: C Compiler Metrics
Keywords: c, compiler, metrics
Message-ID: <1989Sep30.160156.1043@esegue.segue.boston.ma.us>
Date: 30 Sep 89 16:01:56 GMT
References: <1989Sep27.190232.8318@esegue.segue.boston.ma.us>
Sender: compilers-sender@esegue.segue.boston.ma.us
Reply-To: jesup@cbmvax.commodore.com (Randell Jesup)
Organization: Commodore Technology, West Chester, PA
Lines: 19
Approved: compilers@esegue.segue.boston.ma.us

In article <1989Sep27.190232.8318@esegue.segue.boston.ma.us> Steve Lehto  writes:
>  Specifically, how fast must a compiler compile in
>order to be useful?  Is there a "limit of pain", below which the tool is
>considered to be unuseable? 

	How does this give you "the limit of pain"?  It merely tells you
the performance of some compilers.

>Language	Compiler	Target	Host	Speed (lines/min)
>--------	--------	------	----	----------

	An important point you left out: what sort of code?  I have a
compiler that varies by up to 10x in lines/min depending on the source put
into it (it has a global optimizer - _big_ routines annoy it.)
[From jesup@cbmvax.commodore.com (Randell Jesup)]
-- 
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.