PM22827: MISRA_13_4 rule misses violation when used with MISRA_Rule18

APAR status

• Closed as program error.

Error description

• MISRA_13_4 rule states that : The controlling expression of a
  for statement shall not contain any objects of floating type.
  When the attached code is build to detect violations for
  MISRA_13_4 rule, violations are reported as expected.
  However when the MISRA_13_4 rule is used along with the
  MISRA_Rule18, it does not report any violations.
  
  Steps to reproduce:
  ------------------------------
  1) Unzip and load the project in Logiscope 6.6.3
  2) Build the project to observe the violations reported for
  MISRA_13_4 rule
  3) Modify the contents of the GUI.rst file as below:
  
  STANDARD MISRA_Rule18 SEVERITY 'Advisory' ON  END STANDARD
  
  STANDARD MISRA_13_4 SEVERITY 'Required' ON  END STANDARD
  
  4) Build the project again, and observe no violations reported
  this time
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  MISRA_13_4 rule states that : The controlling expression of
  a for statement shall not contain any objects of floating
  type.
  When the attached code is build to detect violations for
  MISRA_13_4 rule, violations are reported as expected.
  However when the MISRA_13_4 rule is used along with the
  MISRA_Rule18, it does not report any violations.
  
  Steps to reproduce:
  ------------------------------
  1) Unzip and load the project in Logiscope 6.6.3
  2) Build the project to observe the violations reported
  for MISRA_13_4 rule
  3) Modify the contents of the GUI.rst file as below:
  
  STANDARD MISRA_Rule18 SEVERITY "Advisory" ON  END STANDARD
  
  STANDARD MISRA_13_4 SEVERITY "Required" ON  END STANDARD
  
  4) Build the project again, and observe no violations
  reported this time
  

Problem conclusion

• Fixed in Rational Logiscope 6.6.3 iFix1.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  TLOGIC LOGISCOP

• Fixed component ID

  5724V81LS

Applicable component levels

• R660 PSN

     UP