Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| C Compiler Metrics stevel@qtc.uucp (Steve Lehto) (1989-09-25) |
| Re: C Compiler Metrics shankar@hpclscu.HP.COM (1989-09-28) |
| Re: C Compiler Metrics jesup@cbmvax.commodore.com (1989-09-29) |
| Date: | Fri, 29 Sep 89 02:56:46 EDT |
| From: | jesup@cbmvax.commodore.com (Randell Jesup) |
| Newsgroups: | comp.compilers |
| References: | <1989Sep27.190232.8318@esegue.segue.boston.ma.us> |
| Organization: | Commodore Technology, West Chester, PA |
| Keywords: | c, compiler, metrics |
In article <1989Sep27.190232.8318@esegue.segue.boston.ma.us> Steve Lehto <stevel@qtc.uucp> 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)]
Return to the
comp.compilers page.
Search the
comp.compilers archives again.