cl6x omit-frame-pointer optimization?

Eric Texley

Dear Community

Some of my colleagues would like to would like to debug C64X code in Code Composer studio with some degree of optimization turned on. When the optimization is turned up, we cannot display the contents of local stack variables, so they have to migrate them to global. Will optimizing for space/speed with Cl6x omit the Frame Pointer and use stack relative addressing to access locals? Is this the reason that we can't see stack variables with optimization turned up? If so, can this particular optimization be omitted?

Thanks,

Eric Texley

over 13 years ago

0 Archaeologist over 13 years ago

TI__Guru* 84285 points

There is no option to directly enable or disable use of a register as the frame pointer. If the frame pointer can be omitted, it will be, regardless of other optimizations.

Optimization necessarily harms debugability.

Please see http://processors.wiki.ti.com/index.php/Debug_versus_Optimization_Tradeoff for a discussion of this topic.

I do not know why you cannot view local variables. What version of Code Composer Studio are you using? What version of the compiler are you using (this is not the same as the CCS version). Can you provide a test case demonstrating the problem?

Code Composer Studio™︎

Code Composer Studio forum

cl6x omit-frame-pointer optimization?