|Linkers - making executables smaller email@example.com (1998-06-18)|
|Re: Linkers - making executables smaller firstname.lastname@example.org (Jerry Leichter) (1998-06-19)|
|Re: Linkers - making executables smaller email@example.com (1998-06-19)|
|Re: Linkers - making executables smaller firstname.lastname@example.org (1998-06-19)|
|Re: Linkers - making executables smaller corbett@lupa.Eng.Sun.COM (1998-06-24)|
|Re: Linkers - making executables smaller email@example.com (1998-06-24)|
|Re: Linkers - making executables smaller firstname.lastname@example.org (1998-06-24)|
|From:||email@example.com (Peter Hall)|
|Date:||18 Jun 1998 11:20:57 -0400|
I have a requirement to make executables smaller. I cannot use
shared libraries. I know there are optimisations on many compilers to
optimise for size rather than speed but I feel that this is only part
of the answer. Have you come across any technologies in which the
linker performs 'global' optimisations? It would seem to me to be
a good place to stick a bunch of size/speed optimisations since the
linker can have access to the whole code. I know that there are
profiling tools but these seem to feed back into the compiler.
Is this an unreasonable request? Is there any real reason why linkers
are stuck in the early 1970s?
Thanks in advance for any information.
[Other than adding support for shared libraries, linkers seem to be
getting dumber as the years pass. I have seen references to globally
optimizing linkers. I think decwrl did one, and the MINIX linker (which
was really the assembler) may have as well. -John]
Return to the
Search the comp.compilers archives again.