[EXT_EP-9211] Use of --check_misra=14.10 causes non-MISRA related warning to be emitted Created: 31/Jan/19  Updated: 19/Feb/20  Resolved: 31/Jan/19

Status: Fixed
Project: Embedded Software & Tools
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Medium
Reporter: TI User Assignee: TI User
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Product: Code Generation Tools
Internal ID: CODEGEN-5843
Forum URL: https://e2e.ti.com/support/tools/ccs/f/81/t/768297
Found In Release: C2000_20.2.0.beta
C6000_8.2.0
C2000_18.1.0.LTS
C6000_8.3.0
ARM_18.12.0.LTS
PRU_2.3.0
ARM_18.1.0.LTS
MSP430_18.1.0.LTS
PRU_2.4.0*
ARM_19.6.0.STS
MSP430_18.12.0.LTS
ARM_20.2.0.beta
C2000_18.12.0.LTS
MSP430_20.2.0.beta
Fix In Release: C2000_20.2.0.beta
C2000_18.1.7.LTS
ARM_18.12.3.LTS
ARM_18.1.7.LTS
MSP430_18.12.3.LTS
C2000_18.12.3.LTS
PRU_2.3.3
PRU_2.4.0*
MSP430_18.1.7.LTS
C6000_8.3.5
C6000_8.2.8
ARM_20.2.0.beta
MSP430_20.2.0.beta
Workaround: No direct workaround. The warning can be suppressed by the usual methods, or corrected as described in the report.
Release Notes: If a local variable's address is taken before the variable is initialised, there will usually not be a warning with default settings. However, if any --check_misra option is used, the compiler will issue a used-before-set warning for the variable.

 Description   

Use of --check_misra=14.10 causes non-MISRA related warning to be emitted


Generated at Tue Apr 08 13:59:48 CDT 2025 using Jira 9.12.17#9120017-sha1:aba4002bcd633f188b6a4bb5dd8a0e1f20b79ee4.