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.

TMS320F280049: How does the user make the compiler warning setting stricter?

Part Number: TMS320F280049

Dear Champs,

I am asking this for our customer.

The user wonder if it possible to make the compiler warning stricter so that they can use it for debugging for potential issues for big projects.

For example, 

variables never used, signed/unsigned data type covert, variables overflow, declare function return

The environment they use now:

CCS v9.0 up and v10.0up

Compiler v16.9.1.LTS.

Please let us know if V16.9.1.LTS can be set here.

If not, is it possible to user new compiler to do so?

Wayne Huang

  • Wayne,

    There are options for the compiler to control this.

    Under Compiler -> Advanced Options -> Diagnostic Options

    You need to know the ID of the issue that you want to change how it is handled.  For example here I have changed 179 (variable declared but not used) to be an error instead of a warning.  The project also changings a couple others to be warnings instead of remarks.  You can get the ID by just building and looking at the problems view or console.  

    Regards,

    John