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
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,6ff6ac051491e437
X-Google-Attributes: gid103376,public
From: dewar@cs.nyu.edu (Robert Dewar)
Subject: Re: GNAT Codesize
Date: 1996/06/21
Message-ID: <dewar.835359186@schonberg>#1/1
X-Deja-AN: 161867206
references: <31c8fdd4.5a455349@zesi.ruhr.de>
organization: Courant Institute of Mathematical Sciences
newsgroups: comp.lang.ada
Date: 1996-06-21T00:00:00+00:00
List-Id: <comp.lang.ada>


Haug said

"Assuming that all the runtime check code is in the runtime
libraries, what is gnat doing? It seems to me that gnat produces
very inefficiente code.

The whole program is never smaller than 400kbyte. Is it possible
to use a dynamic link library for the runtime library? Is there
any chance to reduce the code size?"

You actually have no idea how big your program is, so your guess that
this is gnat inefficiency is incorrect. Undoubtedly you are building
with debugging information present, at least in the runtime library
routines. The debugging informatoin is typically MUCH larger than the
actual code. So strip the objects or executables (depending on your
system) if you want to make the executables smaller (but you won't
be able to debug the resulting program).

These day when 400K of disk space costs 4 cents, most people prefer
to keep the debugging information around which is why this is the
default behavior in the normal setup. 

Note that if you do strip the objects of the library, you must be careful
to preserve the original time stamps.

On some systems it is possible to use a dynamic link library, and the
standard distributions for Linux and SGI do this.
We will probably introduce this in additional distributions as time
goes by.