MATLAB: Do I receive Polyspace compiler errors even though the code looks acceptable

Polyspace Bug Finder

Why do I receive Polyspace compiler errors even though my code looks acceptable?

Best Answer

Be careful about your Polyspace Preprocessor Definitions. You are able to emulate various compiler behavior by adding or even subtracting macros from the preprocessor.

https://www.mathworks.com/help/bugfinder/ref/preprocessordefinitionsd.html

https://www.mathworks.com/help/bugfinder/ref/disabledpreprocessordefinitionsu.html

For example, consider the following line of code. It defines a bitfield member called "MT".

volatile unsigned int MT:1

If one of your Polyspace preprocessor definitions is "MT=0", Polyspace will see the following code when it attempts to compile.

volatile unsigned int 0:1

This will cause a syntax error because the line of code no longer makes sense.

Related Solutions

MATLAB: When is poor customer service acceptable

Todd,

I'm sorry. I wish you were forwarded to me for help. I'm going to email you off of this list to help answer your question and see if there's anything else I can do for you.

Regards,

Paul

MATLAB: Does Polyspace R2017b or later ignore the code annotations

With the old annotation syntax prior to R2017b, you had to put your annotations on the line before the finding you wanted to annotate.

 /* polyspace<RTE:OBAI:High:To fix>  Enter a comment */
 array[in_v3-255] = 0;

With the new annotation syntax your annotation must be on the same line as the finding. This placement is more intuitive and adding annotations does not affect the number of lines in your source code. If you want your annotation to apply to multiple lines, you must specify that explicitly (Please read documentation in details).

So coming back to the previous example, you have to put the annotation on the same line as the finding, or keep it on the line before and add “+1” after the polyspace keyword:

 * /* polyspace +1 RTE:OBAI [To fix:High] "Enter a comment" */
   array[in_v3-255] = 0;
 * array[in_v3-255] = 0; /* polyspace RTE:OBAI [To fix:High] "Enter a comment" */

*Note: *Polyspace R2017b or later still supports code annotations that use the old syntax.

Best Answer

Related Solutions

MATLAB: When is poor customer service acceptable

MATLAB: Does Polyspace R2017b or later ignore the code annotations

Related Question