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.6 required=5.0 tests=BAYES_20,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,6ee3df53165d1873 X-Google-Attributes: gid103376,public From: ct_oreg@vega.concordia.ca (Chris O'Regan) Subject: Re: Ada binaries pretty large Date: 1995/04/21 Message-ID: <3n6v40$66i@newsflash.concordia.ca>#1/1 X-Deja-AN: 101283308 references: <3n51ng$q67@mother.usf.edu> organization: Concordia University, Montreal, Canada nntp-posting-user: ct_oreg newsgroups: comp.lang.ada Date: 1995-04-21T00:00:00+00:00 List-Id: In article <3n51ng$q67@mother.usf.edu> CG := D. Christian Griffin CG>Why are ada binaries (Gnat 2.0.4 on SunOS), at least 230K no matter what CG>the size of the code is (a couple of lines of code). Is there debugging CG>code being added to this? How can I get around this? Have you tried compiling and linking with the "-O2" option? Have you stripped the binary? C programs tend to compile into large binaries as well. (Side note: Just stripped a Linux Gnat binary. Original size: 200Kb; stripped size: 50Kb.) -- ____________________________________________________________ Chris O'Regan Computer Engineering, Concordia University, Montreal, Canada http://www.ECE.Concordia.CA/~ct_orega/addr.html