Re: Typical handling of packages through compilers

[Jeffrey Creem <jeff@thecreems.com>]

Hibou57 (Yannick Duch�ne) wrote:
> Hi all,
> 
> I've noticed that the inclusion of a package, turns into the inclusion
> of all of its content, despite just a few part of it is really used
> (taking into account, internal dependencies). Using seperate data and
> function sections and then the linker gc-section option, does not
> change anything (the executable is even a bit bigger using these
> options).
> 
> There is indeed no implementation requirement about it.
> 
> But I would like to know more on the handling of package through
> various Ada compilers (including Janus if possible, if there are some
> Janus users in the place).
> 
> By the way, on most compilers, is an inner package handled the same
> way a child package is ? I mean... child packages are included only
> when withed, but what about inner packages ? Are they tipically
> included in whole as there are part of another package body or are
> they tipically included only when explicitely referenced (althought
> inner packages does not need to be withed) ?
> 
> Thanks for feed-backs
> 
> 
> P.S. I know GNAT is very famous and widely used, but as it is also
> very expensive (for most of people), it would be nice to have feed-
> back about other compilers, not only GNAT.

A few data other non gnat data points

Most old Ada 83 Verdix (Then Rational) VADS compilers did smart linking 
(at least for vxWorks targets).

Greenhills Ada does it on some platforms (interestingly enough, does not 
  really seem to work for vxWorks targets but I also gave up a bit early)