From: Jose Manuel Lopez-Cepero Newsgroups: comp.os.msdos.djgpp Subject: Re: Optimization idea/RHIDE Date: Sun, 27 Apr 1997 20:38:15 +0200 Organization: Unisource Espana NEWS SERVER Message-ID: <33639D17.4560@ctv.es> References: <335EB17C DOT 5536 AT orland DOT pr DOT tisip DOT no> Reply-To: sigma AT ctv DOT es NNTP-Posting-Host: macarena.ctv.es Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit CC: jorgen AT orland DOT pr DOT tisip DOT no Lines: 36 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk Hi! Jorgen Austvik wrote: > > HI! > > Anywhay, here's my question: > > In M$ VC++ there is a option that lets you choose "Size" or "Speed", > which arguments in the compiler generally favors code speed, and which > favor small code (executable) size??? The size gets dramatically affected by stripping the symbols table (link with -s or use 'strip.exe'), though it will make debugging damn near impossible :-) I use to set quite a lot of optimizations, and it seems like they affect both size and speed. (Most times, -O2 or -O3 make a lot of redundant op's go away, decreasing size by deleting them on the output and speed by saving the processor from executing them ;)) > And, if I get any answers, here's my idea :-) > Why not use theese answers to make to buttons in the RHIDE > Options|Compiler|Optimizations ?? The buttons could check/uncheck the > arguments they were supposed to du, and the gurus could still change it > in any manner they would like... This would be a very nice improvement, you could group the optimizations on profiles and have options to generate .exe's with them... I mean, you could do a non-optimized compile-only run to check syntax, an optimized and stripped run to get a final .exe for a project, etc. -- _* \ |/_|\/||\ sigma AT ctv DOT es _\|\/| ||_\ (formerly Sigmatech) Jerez / Cadiz / Spain