[EXT_EP-7889] Compiler may produce too many reads of one register in one cycle (only on 6200,6400,6700,6400+) Created: 08/Oct/07  Updated: 31/Jan/22

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

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

Product: Code Generation Tools
Internal ID: CODEGEN-115
OldID: SDSCM00023977
Found In Release: C6000_8.2.0
C6000_8.3.0
C6000_8.1.0B1
C6000_7.4.0B1
Workaround: Reduce the SPeed optimization Level.
Use the -ms0, -ms1 switches.

 Description   

This defect is specific to processors that use the -mv6200, -mv6400, -mv6700, and -mv64p/-mv6400+/-mv6500 options (or equivalent --silicon_version options).

This defect does not occur when using the -mv6740 or -mv6600 compiler options or equivalent --silicon_version options.

This defect involves the compiler creating too many reads of a single register on one cycle. The affected processors in question limit the number of reads of the same register in the same cycle to 4 reads. The compiler will generate this type of erroneous code only in rare circumstances and only with the -mv options specified above in the first sentence of this description.

The defect does not occur on 6740 or 6600 CPUs because those processors can have an unlimited number of reads of one register per cycle.

Note that the 8.3.x C6000 C/C++ compiler does not support -mv6200, -mv6400, -mv6700, or -mv67p.

If the compiler generates too many reads of one register per cycle on the affected ISAs/processor, the compiler will emit an error message and fail to produce an assembly file.

If a user encounters this error message, the workaround is to use the -ms0 or -ms1 option which will cause the compiler to not execute certain optimizations that could produce this type of erroneous sequence of code. The use of -ms0 or -ms1 may negatively affect the performance of the compiler emitted code.


Generated at Sat Dec 13 11:36:06 CST 2025 using Jira 10.3.7#10030007-sha1:a563685562f94d165eb4e158cfb2a142338d8c54.