Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!munnari.oz.au!mtiame!jep From: jep@mtiame.mtia.oz (Jesper Peterson) Newsgroups: comp.sys.amiga.tech Subject: Re: Lattice C++ Message-ID: <1990Dec21.055120.9902@mtiame.mtia.oz> Date: 21 Dec 90 05:51:20 GMT References: <1990Dec15.192957.13441@batcomputer.tn.cornell.edu> <716@ncsc1.ATT.COM> Organization: Metal Trades Industry Association, Victoria, Australia. Lines: 21 In article <716@ncsc1.ATT.COM> dcl@ncsc1.ATT.COM (Dave Love) writes: >I haven't seen the Amiga version of gcc yet; hopefully someone who has >can answer a quick question. On UNIX boxes, gcc slurps the entire >input file onto the stack and processes it from there. How was this >handled on the Amiga version? The same. Recommended stack is 100000 or 200000 to be safe. It eats heap as well, I have 1M chip + 2M fast and trying to port Gnu Smalltalk I ran out of memory trying to compile the interpreter module (~100k source file) with optimisation turned on. I squeezed it in by running gcc by hand (ie. not from make) with t: on hard disk instead of ram disk. I am pleased to note that gcc handles the out of memory condition cleanly. I'd bee really interested in seeing g++ as well I might add. I'll be looking for an 8M RAM board RSN I think. Jesper. -- ------------------------------------------------------------------------------ USEnet: jep@mtiame.mtia.oz.au UUCP: ...!uunet!munnari!mtiame.oz!jep [...] I had to leave out reality to keep the post clean and to the point. - jeremy@milton.u.washington.edu (Jeremy York) in rec.music.misc