Page History

evaluation-order

multiple-volatile-accesses

Can detect simple violations of this rule. It needs to examine each expression and make sure that no variable is modified twice in the expression. It also must check that no variable is modified once, then read elsewhere, with the single exception that a variable may appear on both the left and right of an assignment operator

Coverity

EVALUATION_ORDER

Can detect the specific instance where a statement contains multiple side effects on the same value with an undefined evaluation order because, with different compiler flags or different compilers or platforms, the statement may behave differently

ECLAIR

CC2.EXP30

Fully implemented

Can detect violations of this rule when the -Wsequence-point flag is used

35 D, 1 Q, 9 S, 30 S, 134 S

Partially implemented

CERT_C-EXP30-a
CERT_C-EXP30-b
CERT_C-EXP30-c
CERT_C-EXP30-d

The value of an expression shall be the same under any order of evaluation that the standard permits
Don't write code that depends on the order of evaluation of function arguments
Don't write code that depends on the order of evaluation of function designator and function arguments
Don't write code that depends on the order of evaluation of expression that involves a function call

The value of an expression and its persistent side effects shall be the same under all permitted evaluation orders

0400 [U], 0401 [U], 0402 [U],

0403 [U], 0403 [U], 0403 [U],

0404 [U], 0405 [U]

evaluation-order

multiple-volatile-accesses

Exhaustively verified
(See one compliant and one non-compliant example interpreted in the simplified on-line version of the tool.)