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.atari.st,comp.emacs
Subject: Re: GCC: Anyone working on a port?
Message-ID: <594@elmgate.UUCP>
Date: Sat, 28-Mar-87 14:26:57 EST
Article-I.D.: elmgate.594
Posted: Sat Mar 28 14:26:57 1987
Date-Received: Sun, 29-Mar-87 11:55:27 EST
References: <3450@elroy.Jpl.Nasa.Gov>
Reply-To: jdg@aurora.UUCP (Jeff Gortatowsky)
Organization: Eastman Kodak Company, Rochester, NY
Lines: 21
Keywords: C GCC Gnu FSF
Xref: utgpu comp.sys.atari.st:2412 comp.emacs:710

In article <3450@elroy.Jpl.Nasa.Gov> jeff@jplpub1.jpl.nasa.gov (Jeff Skaletsky) writes:
>Now that Richard M. Stallman and the Free Software Foundation have 
>released the first beta test of GCC (Gnu C), is anyone working or 
>planning to work on a port to the Atari ST?
>Jeff Skaletsky
>Jet Propulsion Laboratory

Just a quick overview of the compiler seems to indicate that porting GCC
will NOT be a trivial (nor possibily 'doable') task.  It's sprinkled
with alloca 's  and comsumes 'huge' amounts of memory when optimizing.
Sprinkle in one or two 68000 code generation err's and you begin to get
the picture.  STill it may have tons of code that is 'modifiable' to get
it working on a non-UNIX no-MMU system.....  but lots of it needs
changing.  Remember the ST is FAMOUS for it's horrible memory allocation
routines and this compiler seems to love choking down memory.

-- 
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?