Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!husc6!seismo!rochester!kodak!elmgate!jdg
From: jdg@elmgate.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: GNU C compiler
Message-ID: <595@elmgate.UUCP>
Date: Sat, 28-Mar-87 15:21:32 EST
Article-I.D.: elmgate.595
Posted: Sat Mar 28 15:21:32 1987
Date-Received: Sun, 29-Mar-87 11:54:20 EST
References: <1171@spice.cs.cmu.edu>
Reply-To: jdg@aurora.UUCP (Jeff Gortatowsky)
Organization: Eastman Kodak Company, Rochester, NY
Lines: 17
Keywords: C compiler free
Summary: Getting GCC up on an Amiga appears difficult

We've compiled GCC on a Sun-3 with optimizations on.  The STRIPPED
executable was 400k+.  Further the compiler likes to take it's memory from
the stack. No sweat with an MMU,  but without you'd have to set a fixed
stack size that is possitively huge.  The GCC optimizer really eats memory
fast.  There is a bug or two in it's 68000 (not 020) code generation for
long division, etc...  Anyways good luck.

As a side note: Why does it begin to appear that when your C program
,compiled with Manx 3.4, bombs, you had better check the code it
generated first instead of checking your code first??   8^)


-- 
Jeff Gortatowsky       {seismo,allegra}!rochester!kodak!elmgate!jdg
Eastman Kodak Company  
These comments are mine alone and not Eastman Kodak's. How's that for a
simple and complete disclaimer?