[EXT_EP-10745] Some compiler diagnostic ID numbers changed in releases after 2019 Created: 09/Feb/22  Updated: 08/Sep/25  Resolved: 09/Feb/22

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-9599
Found In Release: C7000_1.4.0.LTS
MSP430_20.2.0.LTS
C7000_2.1.0.LTS
MSP430_21.6.0.LTS
C2000_21.6.0.LTS
C6000_8.3.5
ARM_20.2.0.LTS
C2000_20.2.0.LTS
Fix In Release: C7000_2.1.1.LTS
ARM_20.2.7.LTS
C2000_20.2.7.LTS
MSP430_21.6.1.LTS
C6000_8.3.12
C7000_1.4.3.LTS
C2000_21.6.1.LTS
MSP430_20.2.7.LTS
Affected Platform/Device: default

 Description   

In July 2019, a change to the compiler inadvertently caused some existing
diagnostic numbers to change.

As of February 2022, the defect has been fixed so the previous diagnostic numbering is restored.

Therefore, if you were working with a compiler released after July 2019, and you are using compiler options that control compiler diagnostics (for example, the compiler option --diag_suppress), and you migrate to a compiler released after February 9, 2022, you may need to adjust the compiler diagnostic number parameter by lowering the diagnostic number by 1 to match the corrected numbering. This change will not be necessary for most diagnostic numbers.

For example, --diag_suppress 2681 should now be written as
--diag_suppress 2680.


Generated at Fri May 01 09:57:39 CDT 2026 using Jira 10.3.7#10030007-sha1:a563685562f94d165eb4e158cfb2a142338d8c54.