
Difference in 4.2 and 5.0?
We've seen a similar problem when optimize for speed is turned on in the
tree control or in places where we have member functions that take
different paramater lists. If we set optimizations to size instead of speed
then things are OK, but optimize for speed seems to break for us. Is this
similar to what you're seeing?
Quote:
> Hi,
> I have been using VC++4.2 to optimize Assembly code and have now shifted
> to VC++5.0. Some of my projects have stopped working after I made the
> change. On stepping through I found that for some sub-routines the Stack
> pointer was offset by 4 bytes almost as if something else was pushed on
> to the stack during the subroutine call.