Re: VC++ 7.0 makes programs that run slower than VC++ 6.0

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

>No floating point, just integer. The only things besides POD are structs of POD,
>std::string, and std:: vector of POD or structs.

Are you compiling the VC7 build with the run-time diagnostics options?
They'll add some overhead, which may be significant in a large tight
loop.

Failing that, the likelihood is that you're seeing differences because
of the heap memory management (you're using strings and vectors).

You need to come up with some example code that illustrates the
differences before people can have a more informed guess as to why the
difference is so noticeable.

Dave
.

Relevant Pages

  • Re: Managed vs Unmanaged Bare Bones Performance Test
    ... just the basic stuff inside the CLR i.e. function calling ... both call a function passing an int by value from inside a for loop. ... //record the overhead for calling the performance counter API ...
    (microsoft.public.dotnet.framework)
  • Re: Assembly string functions in i386 libc
    ... of string functions on i386? ... for the usual overhead for string instructions). ... The cmpb in this takes 2 cycles, but the loop overhead takes no more ... versions using the string instructions are much ...
    (freebsd-arch)
  • Re: For Loop minimisation
    ... seconds to execute that loop.. ... call overhead. ... bother trying to vectorize. ... The cost is all inside. ...
    (comp.soft-sys.matlab)
  • Re: Managed vs Unmanaged Bare Bones Performance Test
    ... virtual machine and JIT will give the same performance as native C++ compiler ... both call a function passing an int by value from inside a for loop. ... //record the overhead for calling the performance counter API ...
    (microsoft.public.dotnet.framework.clr)
  • Re: defered word options
    ... purpose and the same large nested outer loop structure can ... inside of the loop have their overhead multiplied by the number ... implementation of defered words is simply a jump opcode. ... It is of course an example of using self-modifying code ...
    (comp.lang.forth)