Re: optimizing c++ code (on win32 platform), all the techniquesyou know?

"cody" <deutronium@web.de>
27 Sep 2003 13:59:23 -0400

          From comp.compilers

Related articles
optimizing c++ code (on win32 platform), all the techniques you know? tzuchien_chiu@xgitech.com (Tzu-Chien Chiu) (2003-09-22)
Re: optimizing c++ code (on win32 platform), all the techniquesyou kno tkfx@yahoo.com (Alex Blekhman) (2003-09-23)
Re: optimizing c++ code (on win32 platform), all the techniquesyou kno deutronium@web.de (cody) (2003-09-27)
| List of all articles for this month |

From: "cody" <deutronium@web.de>
Newsgroups: comp.lang.c++,comp.os.ms-windows.programmer.win32,comp.compilers
Date: 27 Sep 2003 13:59:23 -0400
Organization: Compilers Central
References: 03-09-070
Keywords: performance
Posted-Date: 27 Sep 2003 13:59:23 EDT

> * Boost.Pool - a fast memory allocation algoritm, fixed-size chunks.
> <http://www.boost.org/libs/pool/doc/index.html>


when you use it wrong, you need much more memory than you actually need.


> * Whole Program Optimization with Visual C++ .NET
> <http://www.codeproject.com/tips/gloption.asp>
> I almost turn on every possbile Visual C++ options to optimize the
> speed.


Good idea, but some options can under certain circumstances create
errors in your executable


> * inline every possbile function


That is very stupid. inlining very small functions that are called in
loops can be a good idea, but inlining every function in the program
is just stupid because it bloats the code which then makes code
caching very unefficient.


> * Recompile the CRT with _fastcall calling convetion


This can lead to errors too. be very careful.


As the foreposter said, before you start wasting your time with
useless things like spending 90% time on things that comsumes 0.01% of
performance, detect what certain loops are slow, instead of
bit-fiddling rethink your algorithms.


--
cody


Freeware Tools, Games and Humour
http://www.deutronium.de.vu


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.