> I noticied that CW6 with no optimization enabled had the quite bad
idea to
> not even do stack allocation : when it encounters a variable it just
append
> it in the stack resulting in stack frame frequently twice the
necessary
> size...
> It results in crashes at debug you do not have at release.
Yep. This is actually intentional -- the debug code keeps all variables
distinct and doesn't allocate anything to registers so you have full
visibilty into all items and nothing aliases anything else. Without
this, MW would get even more "complaints" about stepping through the
debugger and seeing an assignment changing multiple variables.
> The first level of optimization is enough to avoid this problem.
Yes, at that level, some register allocation is done, which greatly
reduces stack pressure by keeping lots of small values in registers for
their lifetimes.
--
Ben Combee, [EMAIL PROTECTED]
Techwood Broadcasting Foundation, Austin Bureau
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
