From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!jpl-devvax!usenet From: larryc@poe.jpl.nasa.gov (Larry Carroll) Newsgroups: comp.lang.ada Subject: Re: Reducing size of Ada's EXE files Message-ID: <1991Apr12.235101.7245@jpl-devvax.jpl.nasa.gov> Date: 12 Apr 91 23:51:01 GMT References: <437@wrdis01.af.mil> Sender: usenet@jpl-devvax.jpl.nasa.gov (For NNTP so rrn will be able to post) Organization: Jet Propulsion Lab, AEG/FIST Nntp-Posting-Host: poe List-Id: What most of us complain about is the amount of code that gets linked into an executable which will never be executed. On DEC Ada, for instance, whenever you used a subprogram from a package, you got the whole package linked in. So if the subprogram was 3 KBytes & the package was 3 MBytes, you got a 1000 times as much code in your executable. Agreed, it takes a smart linker to know just what part of a package you need. For instance, any variables global to a package which are used by the desired subprogram will need to be linked in. Any initialization code you include at the end of the package, & all the subprograms & global variables they use, must be linked. And so on. But eventually such smart linkers must become available if Ada is to compete successfully with other languages. Anyone know which vendors supply such linkers? Larry Carroll puente.jpl.nasa.gov