Newsgroups: comp.os.msdos.djgpp From: Elliott Oti Subject: Re: RHIDE and pentium cc1plus Sender: usenet AT fys DOT ruu DOT nl (News system Tijgertje) Message-ID: In-Reply-To: <9hAZ.3264$sN3.543198@news21.bellglobal.com> Date: Fri, 17 Apr 1998 09:52:32 GMT Content-Type: TEXT/PLAIN; charset=US-ASCII References: <9hAZ.3264$sN3 DOT 543198 AT news21 DOT bellglobal DOT com> Mime-Version: 1.0 Organization: Physics and Astronomy, University of Utrecht, The Netherlands Lines: 32 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk On Fri, 17 Apr 1998, Paul Derbyshire wrote: > It can't possibly be malloc failure, since there's no way in hell cc1plus is > using over 62 megs in compiling! Besides, even if it were using 62 megs it > would have the exact same problem at the command prompt, which it does not. > > So what is wrong with PGCC? What other circumstances will make it emit that > error message? Environment space perhaps? RHIDE will fill its environment and > that of any subtask with $RHIDE_COMPILE_FLAGS and so forth, so that could be > it, except I just don't see why cc1plus would use environment space as internal > storage. > I find that compiling c++ programs with large source-files that make heavy use of templates with gcc, uses enourmous amounts of memory, especially if all optimizations are enabled, or recursive or nested templates are heavily used. Try compiling the project without any optimizations first, in plain DOS with cwsdpmi as your dpmi provider. Make sure you have at least 100 meg disk space free before running 'make'. You could also try and see if you can compile your project piecemeal -- ie compile your *.cc files separately on the command line, and link the resulting *.o files together. At the very least this should give you the files gcc chokes on, and you can post relevant code sections (or if the source is huge, set it on the Web somewhere). Cheers, Elliott Oti kamer 104, tel (030-253) 2516 (RvG) http://www.fys.ruu.nl/~oti