QA·C Help - 2891

	2891	Definite: Negative value implicitly converted to an unsigned type.

Conversion to unsigned

A definite anomaly has been detected. The value of an object or a non-constant expression is being converted to an unsigned type and dataflow analysis has determined that the value is always negative. Is this really intended ? The operation is well defined but is likely at best to be confusing.

The unsigned value which results will the be the value obtained by repeatedly adding or subtracting one more than the maximum value that can be represented in the new type until the value is in the range of the new type.

For example, in the following code, if char is an 8 bit type, the value assigned to ucx will be the value obtained by repeatedly adding 256 to the value of sia until a non-negative value is achieved..


/*PRQA S 290,2017,2983,2986,3199,3203,3227,3408 ++*/
void foo(int sia)
{
    unsigned char ucx;

    if (sia < 0)
    {
        ucx = sia;               /* 2891 3757 */
    }
}

MISRA-C:2004 Rules applicable to message 2891:

Rule 21.1 (Required)

Minimisation of run-time failures shall be ensured by the use of at least one of (a) static analysis tools/techniques; (b) dynamic analysis tools/techniques; (c) explicit coding of checks to handle run-time faults

See also:

2890 Constant: Negative value implicitly converted to an unsigned type.
2892 Apparent: Negative value implicitly converted to an unsigned type.
2893 Suspicious: Negative value implicitly converted to an unsigned type.
2895 Constant: Negative value cast to an unsigned type.
2896 Definite: Negative value cast to an unsigned type.
2897 Apparent: Negative value cast to an unsigned type.
2898 Suspicious: Negative value cast to an unsigned type.

QA·C Source Code Analyser 8.1
MISRA-C:2004 Compliance Module 3.2
© 2012 Programming Research.
www.programmingresearch.com

Personality Groups | Glossary | Message Index | MISRA-C:2004 Rule Index

Contents