> I know the linker is verry slow but the compiler isn't verry fast
> either, this can be clearly seen on slower machines, Delphi somehow
> manages to compile and link everything verry fast, about 10x faster
> wich is impressive with all the bloat it has, while using Lazarus i
> can see when linker gets into action or i think i do, can someone tell
> me what's the best way of knowing when the linker gets into action, i
Compiling with -E will skip the linking part. That will give you an idea
how fast the compiler itself is.
But the main priority for fpc is maintainability and only after that comes
speed. There are a couple of know places that could be optimized for
speed, but for now it is "don't change things that work".
> don't know who could make a better linker cause this one has support
> for many app types, a compiler with a built-in linker would probably
> do a better job.
I can create an internal linker. But i don't have time for fpc for the
rest of 2005. The most challenging and time consuming part of creating a
linker is the debugging/analysing of problems with faulty generated
applications.
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives