• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 507 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.

C6000 Compiler Option For Function Level Profiling

Martin Roadnight
Prodigy 20 points


I have a question about the debugger compiler option that I should use when using the profiler to get a cycle count for a subroutine. I know that the -g option should be avoided, because it gives an inflated result, but should I use the '--symdebug:none' or '--symdebug:skeletal' option?

If I suppress all debug, the inclusive count for the calling routine is 322. Using the skeletal debug, the count I get for the subroutine alone is 2324. Which is correct?

Thanks,

Martin

  • 0
    TI__Guru**** 173310 points

    Martin Roadnight said:

    I have a question about the debugger compiler option that I should use when using the profiler to get a cycle count for a subroutine. I know that the -g option should be avoided, because it gives an inflated result, but should I use the '--symdebug:none' or '--symdebug:skeletal' option?



    The CCS profiler needs at least minimal symbolic debug information to do function profiling, which is provided by the --symdebug:skeletal option  You can either explicitly add this option or not specify any --symdebug options at all (that will default to skeletal debug info).