WOW! I really hope that this will fix the
problem. I will check it tomorrow, but can you please let me know
what does this flag do?
check on the internet, its a well known gotcha which has been fixed
in VS2010. basically, it disable some iterator checking which is
strangely active even in release mode.
Another question! Do I have to add the line
#define _SCL_SECURE 0
to all my header and code sources even source of GMM++ or just on
my own source files or even on file is enough?
easiest way is to add /D"_SCL_SECURE=0" (or the like) to your
command line when compiling your code *and* gmm (if its not header
or add it first in all the C++ files.
What about those pragmas you mentioned?
check msdn. if needed add, they must be defined before including the
On 2010-10-08 10:09, Cédric Venet wrote:
try to define _SCL_SECURE=0 (warning ABI incompatible so all the
code you link must use this flag)
for code using the stl heavily, it can result in 100x speedup.
and check all the optimisation are on.
On 07/10/2010 23:23, Danesh Daroui wrote:
> I have recently ported our code written with GMM++ to
> and recompiled the code in Visual Studio 2008. The weird
> that when I run the code, GMM++ function compiled with
> 2008 has extremely poor performance comparing to the old
> compiled with MingW on Windows. I also compiled the code
> C++ Compiler 11.1 in Visual Studio 2008, and the
> GMM++ functions were still very very low and they worked
> What is the reason? I thought, maybe the GMM++ code is
> compiled with gcc, but in the web site it is stated that
> compatible with Intel C++ Compiler 8.0. Has anybody had
> list address@hidden
Lulea University of Technology
Cell phone: +46-(0)704-399847