Re: size_t
From: assaarpa (redterminator_at_fap.net)
Date: 09/20/04
- Next message: JKop: "Re: signed int overflow"
- Previous message: JKop: "Re: signed int overflow"
- In reply to: Peter Koch Larsen: "Re: size_t"
- Next in thread: Ioannis Vranos: "Re: size_t"
- Reply: Ioannis Vranos: "Re: size_t"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 20 Sep 2004 12:16:39 +0300
> Far more interesting is the project settings. Are you running debug code?
> What optimizations are involved? Running in debug mode could easily
penalise
> std::list more than assaarpa::list.
I never profile debug builds. For each compiler the settings are the
defaults and only few settings tuned to favour speed (/O3, /Ox, or similiar
depending what compiler was used) with very little furry dices or other
spices thrown in.
Here's the Bill Gates settings:
/Ox /D "WIN32" /D "NDEBUG" /D "_CONSOLE" /D "_MBCS" /FD /EHsc /ML /GS /FAs
/Fa"Release/" /Fo"Release/" /Fd"Release/vc70.pdb" /W3 /nologo /c /Wp64 /Zi
/TP
(that conflicts with what I wrote above, because that is copy-pasted from
Command Line -output window of the solution settings, only change I did was
to switch O2 to Ox after creating a fresh solution).
g++ settings:
-g -Wall -I$(incbase) -O3 $(libs)
So in practise only -O3 that directly affects code generator, if there are
any specific settings you would like me to try please post them.
- Next message: JKop: "Re: signed int overflow"
- Previous message: JKop: "Re: signed int overflow"
- In reply to: Peter Koch Larsen: "Re: size_t"
- Next in thread: Ioannis Vranos: "Re: size_t"
- Reply: Ioannis Vranos: "Re: size_t"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]