From: | "Tzvetan Mikov" <ceco@jupiter.com> |
Newsgroups: | comp.compilers |
Date: | 10 Aug 2002 02:00:23 -0400 |
Organization: | Concentric Internet Services |
References: | 02-07-098 02-07-121 02-07-128 02-08-005 |
Keywords: | optimize, practice |
Posted-Date: | 10 Aug 2002 02:00:23 EDT |
"Joachim Durchholz" <joachim_d@gmx.de> wrote in message
> I'm under the impression that compilers spend most of their time with
> optimization. TP did constant expression evaluation and dead code
> elimination, but that's about all: no liveness analysis, no register
> allocation. The resultant machine code was horrendous (but nobody
> noticed or cared, even in the 16 MHz age - so much for the relevance
> of efficiency).
>
> That's Turbo Pascal. I never got around to looking at Borland Pascal
> output - I sincerely hope things have improved.
They have, but not as much as one would hope (or expect, given how much time
has passed). All 32-bit versions of Borland Pascal/Delphi use Borland C's
backend which performs some of the standard optimizations. Unfortunately the
last time I looked (Borland C++ 5.5, 2000) it was still pretty horrible
compared to GCC or VC (not to mention Intel). I used to be a long time
Borland fan but I got pretty angry when I saw things like:
mov eax, ebx
mov ebx, eax
in the "optimized" code.
-tzvetan
Return to the
comp.compilers page.
Search the
comp.compilers archives again.