Re: Size of linked program increasing with new version of GNAT.

[Georg Bauhaus <bauhaus@futureapps.invalid>]

"Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> wrote:
> On Wed, 31 Dec 2014 04:08:13 -0800 (PST), Jean François Martinez wrote:

>> The executable is parasited by
>> things like runtime, libraries, dynamic linker (or first stage of dynamic
>> linker) and so on.
> 
> The code size can be approximated by a linear function A + B*x, where x is
> the program "complexity". Arguments that A might be irrelevant is true only
> if B is correspondingly small compared to the alternatives so that with
> growing x you could compensate your losses on A.

Executables' size also reflects technical needs: compressing an
executable program such as gnatmake shows ratios of
over one half on Intel. Chances are, then, that there is redundant
executable code in gnatmake. But there are reasons that there is,
I guess, because the optimizers make the processor perform better,
reflecting its sets of instructions and its architecture (parallel
pipelines etc.). When TIME is more important than SPACE
in order to meet timing requirements, greater code size might
seem paradoxical, but might be necessary.

Has anyone tried deduplication with executables?