LD being resource hungry while trying to achieve maximal dead-code elimination

LD being resource hungry while trying to achieve maximal dead-code elimination

[Marco van de Voort]

I'm using FPC (www.freepascal.org), which has a mode (called smartlinking)
that tries to achieve maximal (or at least several magnitudes more optimal)
dead-code elimination by creating archives that contain a compilation unit
per symbol.

While this works fine in general, LD's memory usage is a becoming a problem.

The memory usage is roughly 100-200 times the size of the generated binary,
is there any somewhat easy way (small mods and recompiling inclusive) to
decrease this?

P.s. if people argue that this method is a dirty hack, I fully agree.
Another way to achieve the same result would be appreciated. The hack is
probably introduced years ago, maybe there is a better way meanwhile.

Re: LD being resource hungry while trying to achieve maximal dead-code elimination

[Hans-Peter Nilsson]

On Thu, 17 Jul 2003, Marco van de Voort wrote:

> I'm using FPC (www.freepascal.org), which has a mode (called smartlinking)
> that tries to achieve maximal (or at least several magnitudes more optimal)
> dead-code elimination by creating archives that contain a compilation unit
> per symbol.

> P.s. if people argue that this method is a dirty hack, I fully agree.
> Another way to achieve the same result would be appreciated. The hack is
> probably introduced years ago, maybe there is a better way meanwhile.

The equivalent of gcc -ffunction-sections -fdata-sections?
(But don't forget to also emit constants in separate sections,
unlike gcc.)

brgds, H-P