The issue of "Potentially unprotected variable" arises in Polyspace Code Prover when analyzing multitasking programs. By default, Polyspace does not analyze concurrent tasks unless you enable it. For more details, refer to the Polyspace documentation on https://www.mathworks.com/help/codeprover/ug/analyze-multitasking-programs-in-polyspace.html
If you prefer not to use semaphores or similar synchronization mechanisms to address the unprotected access warnings, consider the following workaround:
- Specify Temporally Exclusive Tasks: You can artificially specify that all tasks accessing the global shared variable are temporally exclusive. This means treating them as if they do not run concurrently, even if they might during actual execution. This approach will:
- Change the variable's flag from orange to green, indicating no unprotected access.
- Eliminate the need to review these specific checks.
- Ensure that other runtime checks remain unaffected.
For further information on how to specify temporally exclusive tasks, use cases and corner cases is available at the documentation page linked here:
Alternatively, if the requirement is to filter out the results for this check from the report, this could be done by using the documentation page linked here:
