Forcing local variable with "volatile" is just unaceptable this will result in very slow and unoptimized code once debuging is finished (unless removing volatile the keyword )!
normaly If gcc is at o0 is is should not optimize anything so every single variable is on stack and every single access do access the stack, also at o0 it should be any strange things due to instruction scheduling and overs optimization ...
I've use over mcu with gcc and sure code was almost not debugable at o2 and o3 but at 01 and further more o0 debugability was fine...
Look like with ride/circle even without optimizing the debuger is lost and debuging is almost impossible ...
Last edited by diabolo38 (2010-06-22 16:53:27)
.