[EXT_EP-9214] Compiler schedules an M-unit instruction too soon after MPYSP2DP or MPYSPDP Created: 14/Jan/19 Updated: 19/Feb/20 Resolved: 14/Jan/19 |
|
| Status: | Fixed |
| Project: | Embedded Software & Tools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | High |
| 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-5777 |
| Found In Release: | C6000_8.2.0 C6000_8.3.0 C6000_8.1.0B1 |
| Fix In Release: | C6000_8.3.3 C6000_8.2.6 |
| Workaround: | Avoid mixing single and double-precision when using float multiplication, or use compiler option --legacy |
| Release Notes: | The compiler may place an M-unit instruction too close after either a MPYSP2DP or MPYSPDP instruction. This corrupts the functioning of one of the M-unit instructions. |
| Description |
|
Compiler schedules an M-unit instruction too soon after MPYSP2DP or MPYSPDP |