• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 3278 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

#pragma message equivalent for TI compiler

Anuj Aggarwal
Expert 3990 points

Hi,

I need help in closing the thread below, it is regarding #pragmas for TI compiler:

http://e2e.ti.com/support/dsp/tms320c6000_high_performance_dsps/f/112/t/93658.aspx

Thanks.

  • 0
    TI__Guru**** 244930 points

    Thanks to Archaeologist for providing the correct answer.  Use #warn instead.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Expert 2290 points

    Hi, as the original poster wrote in the other thread, #warn is not fully equivalent to #pragma message, otherwise #pragma message wouldn't exist!

    #warn prints its argument directly as a string, while #pragma message can perform preprocessor substitutions to enable "tricks" like printing the compile-time value of a macro, as shown by the OP in the other thread and in more detail here .

    If there is any other way to see the compile-time value of a macro I am very interested!

    Thanks,

    Giannis

  • 0 in reply to Giannis Roussos
    TI__Guru**** 244930 points

    Giannis Roussos said:
    If there is any other way to see the compile-time value of a macro I am very interested!

    Consider using the option --gen_acp_raw.  It is documented in the compiler manual for your target CPU. All of those manuals can be accessed on this page.

    Thanks and regards,

    -George