Xref: news2.mv.net comp.os.msdos.djgpp:7830 From: Thomas Demmer Newsgroups: comp.os.msdos.djgpp Subject: Re: lots of disk access when linking? Date: Wed, 21 Aug 1996 12:10:16 +0100 Organization: Lehrstuhl fuer Stroemungsmechanik Lines: 39 Message-ID: <321AEE98.167E@LSTM.Ruhr-UNI-Bochum.De> References: <01bb8ef5.847655a0$06020690 AT cam DOT utas DOT edu DOT au> NNTP-Posting-Host: bvb.lstm.ruhr-uni-bochum.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Ryan Boyes wrote: > > Whenever I compile and link any source(usually from rhide) there is a lot > of accessing the HD. The classic "Hello World" source takes up to two > minutes to compile and link. Isn't this a bit long? Sure. At least you should have SMARTDRV or some other cache mechanism activated. (Although, 2 min. are _V_E_R_Y_ long). See the FAQ for an example how to optimise your machine's setup. > > Also, the available memory, in the top right hand corner of the IDE does > not change during the compile/link process (should it?). This suggests > that the process is relying exclusively on the TMPDIR that is set in my > autoexec.bat. Is there an option for gcc that I should set to get gcc to > utilize my 16Mb of ram? Well, it automagically uses whatever RAM it can grab. This one's for the developers: I just put the alpha release ld.exe on my Netware server: Link times for a 12 line prog went down to 3 seconds, compared to 4 seconds with the ld.exe of V2.0 and all files local. Great Job! -- Ciao Tom ************************************************************* * Thomas Demmer * * Lehrstuhl fuer Stroemungsmechanik * * Ruhr-Uni-Bochum * * Universitaetsstr. 150 * * D-44780 Bochum * * Tel: +49 234 700 6434 * * Fax: +49 234 709 4162 * * Voice/Fax Box: +49 2561 91371 2056 * * http://www.lstm.ruhr-uni-bochum.de/~demmer * *************************************************************