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=1.3 required=5.0 tests=BAYES_00,INVALID_MSGID, MSGID_RANDY autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,22fbdbb6ab08eb4a X-Google-Attributes: gid103376,public From: Robert Dewar Subject: Re: Basic questions about Ada95 Date: 1999/08/02 Message-ID: <7o4hq7$rkt$1@nnrp1.deja.com>#1/1 X-Deja-AN: 507992433 References: <933315145.641@www.remarq.com> <37A59BE2.38395082@maths.unine.ch> X-Http-Proxy: 1.0 x24.deja.com:80 (Squid/1.1.22) for client 166.72.70.147 Organization: Deja.com - Share what you know. Learn what you don't. X-Article-Creation-Date: Mon Aug 02 16:42:49 1999 GMT X-MyDeja-Info: XMYDJUIDrobert_dewar Newsgroups: comp.lang.ada X-Http-User-Agent: Mozilla/4.04 [en] (OS/2; I) Date: 1999-08-02T00:00:00+00:00 List-Id: In article <37A59BE2.38395082@maths.unine.ch>, Gautier wrote: > > 2.Is the size of the executables in an acceptable range? Note that critical factors here are: 1. Optimization level, optimized code will generally be smaller, but enabling inlining may make it larger. [C has no language controlled inlining so is not subject to this behavior, but of course cannot get interunit inlining either] 2. Debugging symbols. With some compilers compiling with debugging information can make executables much larger (although typiccaqlly this is not information that is part of the footprint of the application in memory). 3. Static vs Dynamic linking. Particularly in small programs, whether the runtime library is statically or dynamically linked can make a huge apparent difference in executable sizes. Sent via Deja.com http://www.deja.com/ Share what you know. Learn what you don't.