From: Damian Yerrick Newsgroups: comp.os.msdos.djgpp Subject: Re: upgrade chaos Organization: Pin Eight Software Message-ID: <5dap7scv7eqctngqmo3csv14r690qjj48t@4ax.com> References: <387C3BB5 DOT A52F776C AT mpx DOT com DOT au> X-Newsreader: Forte Agent 1.7/32.534 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 19 X-Trace: /wObncl0ojGV0MN1vaMc4SsdyGpFl8u8Udkm1E+bG7KLKasvzSUsNnzn8asDjamOr1NquxO61Lk/!m7Si5X4UF1XDywHcyCf7s4/g5zHwGHCOmzPGsZi1q9lKm3WxVIpw5IMzV130XZYlP4neon8pyQ== X-Complaints-To: abuse AT gte DOT net X-Abuse-Info: Please be sure to forward a copy of ALL headers X-Abuse-Info: Otherwise we will be unable to process your complaint properly NNTP-Posting-Date: Wed, 12 Jan 2000 16:25:36 GMT Distribution: world Date: Wed, 12 Jan 2000 16:25:36 GMT To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Eli Zaretskii wrote in message ... > >This usually means a hardware problem. GCC is a memory hog: GNU programs tend to eat memory. But this is OK; the environments (DOS+CWSDPMI+DJGPPCRT, Linux+glibc) they run in are good at virtual memory management. It means that a RAM upgrade will upgrade the speed of all of GNU. >It is not uncommon for it to be the first application that >crashes when something is wrong with memory or CPU cache setup. Who needs expensive diagnostic software to find memory problems? Just run GCC on a rather large source file. :-) -- Damian Yerrick http://yerricde.tripod.com/ View full sig at http://www.rose-hulman.edu/~yerricde/sig.html