• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 343 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

Compiler/TMS320F28374S: CPU registers ST0 and ST1, in which case they need POP and PUSH

Compiler/TMS320F28374S: Debugging model

Jordan Zhou
Genius 10180 points
Part Number: TMS320F28374S


Tool/software: TI C/C++ Compiler

Hi,

There are several options for debugging model, like symdebug:coff, symdebug:dwarf and symdebug:profile_coff.

We'd like to know, will these three models impact customer's application function?

Just an example: with symdebug:dawrf, the *.out is generated; it will be converted to *.bin and then download to C2000. Application function works well. The same to symdebug:coff.

But when switch to symdebug:profile_coff, the application function can't work well.

What's your suggestion on the debugging model?

Thanks a lot.

Br, Jordan

  • 0
    TI__Guru**** 251230 points

    You must be using an older version of the compiler.  Recent versions of the compiler do not support --symdebug:coff or --symdebug:profile_coff.  

    In older compilers, the options --symdebug:dwarf and --symdebug:coff cause the compiler to reduce the effectiveness of certain optimizations in order to make it easier to debug the code.  The option --symdebug:profile_coff does not reduce the effectiveness of any optimization, in part by issuing less debug information.  Enough debug information is issued so function level profiling still works, but no more than that.

    So, by changing from --symdebug:coff to --symdebug:profile_coff, you increase the amount of compiler optimization.  That this causes the application to fail may mean there is a problem with the compiler.  More often, though, it means some problem in the application is present all the time, but only increased optimization uncovers it.

    Thanks and regards,

    -George