Xref: utzoo comp.sys.amiga.hardware:5884 comp.unix.amiga:108
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!lll-winken!uunet!mcsun!ukc!harrier.ukc.ac.uk!mr3
From: mr3@ukc.ac.uk (M.Rizzo)
Newsgroups: comp.sys.amiga.hardware,comp.unix.amiga
Subject: Re: unix and memory, sigh (was Re: What Happens If You Have > 9 Meg??
Message-ID: <6766@harrier.ukc.ac.uk>
Date: 29 Jan 91 11:32:22 GMT
References: <1991Jan26.054948 <1991Jan27.183019.18321@scuzzy.in-berlin.de> <1991Jan28.052517.909@kessner.denver.co.us>
Reply-To: mr3@ukc.ac.uk (M.Rizzo)
Followup-To: comp.sys.amiga.hardware
Organization: Computing Lab, University of Kent at Canterbury, UK.
Lines: 22

In article <1991Jan28.052517.909@kessner.denver.co.us> david@kessner.UUCP (David D. Kessner) writes:
>In article <1991Jan27.183019.18321@scuzzy.in-berlin.de> src@scuzzy.in-berlin.de (Heiko Blume) writes:
>>>	GCC's executeable is about 1.8 meg.
>>sounds like you compiled it with -g and didn't strip it.
>>my gcc-cc1 is 477KB.
>
>Well.  I didn't see the -g option, but I did strip it.  What's the -g option?
>You always wanted to discuss UNIX, GNU, X-Windows, and i386's on the Amiga 
>news group...

The -g option is for debugging - it causes the compiler to generate
extra info in the object code for use by a debugger such as gdb
(GNU debugger). Part of the reason for the large difference in code
could be due to the processor. I would expect the code for a RISC 
processor such as the SPARC to be much larger than the 680x0 equivalent.
Here the size of gcc-cc1 is about 1.6 meg (compiled with -g on a
SUN SPARC).


>					David Kessner

Mike Rizzo