• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 82 subscribers
  • Views 403 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.

Original question:

TMS320F28377D-Q1: What does warning "#30013-D" mean?

TMS320F28377D-Q1: MISRA-C and this compiler warning #30013-D

Wayne Huang
Genius 15560 points
Part Number: TMS320F28377D-Q1

Dear Champs,

I am asking this for our customer.

We are aware of this issue and have encountered this issue.

https://software-dl.ti.com/ccs/esd/documents/cgt-cl2000-v18.12.x_cla-signed-integer-comparison-workaround.html

But because this is for automotive application and MISRA-C requirement is needed, which does not support using float comparison.

Therefore, we have to face this warning 

warning #30013-D

Even the report to suppress it is not resolved.

https://sir.ext.ti.com/jira/browse/EXT_EP-9814

Therefore, do you have any suggestion if the user has to meet MISRA-C and this issue?

Just keep the warning?

Wayne Huang

  • 0
    TI__Mastermind 32345 points

    Hi,

    Have you tried the manual workarounds mentioned in the page?

    Regards,

    Veena

  • 0 in reply to Veena Kamath
    TI__Genius 15560 points

    Dear Veena,

    The user tried the workaround by using floating comparison and it worked.

    Now, the problem is MISRA considerations for automotive application.

    Another one is, can the user still use integer comparison and suppress the warning if they don't think they will violate it?

  • 0 in reply to Wayne Huang
    TI__Mastermind 32345 points

    There are some other manual workarounds mentioned in the page apart from the compiler workaround. Have you tried those?

    diag_suppress just suppressed the specified warning IDs. Using that option and just ignoring the generated warning is functionally the same. If you are are sure there is no functional impact, you mat ignore that warning.

    Regards,

    Veena