| ID |
Summary |
State |
Reported In Release |
Target Release |
Workaround |
Release Notes |
| CODEGEN-2119 |
Stack usage assistant call graph misses callee relationship for some direct calls |
Fixed |
ARM_16.9.0.LTS |
ARM_16.9.3.LTS |
|
The Object File Display utility failed to detect function callees when generating call graph information for functions that contain nested blocks. |
| CODEGEN-2098 |
Temp filename collisions on Windows with many parallel invocations |
Fixed |
ARM_16.9.0.LTS |
ARM_16.9.3.LTS |
|
In some cases with a large number of compilations in parallel on Windows, the compiler could create temporary files with colliding names, resulting in strange compilation failures. |
| CODEGEN-2060 |
Even though option --buffer_diagnostics is not used, compiler issues diagnostic that says it is deprecated |
Fixed |
ARM_16.9.0.LTS |
ARM_16.9.3.LTS |
None |
The --buffer_diagnostics compiler option was deprecated as of MCU compilers v16.6.0.STS because this setting became the default behavior for the compiler. However, the option was passed to the linker and the linker issued a remark stating the option was deprecated. |
| CODEGEN-2053 |
Compiler incorrectly reorders struct assign for small, volatile structs with bit-fields |
Fixed |
ARM_16.9.0.LTS |
ARM_16.9.2.LTS |
Use optimization level 0 or off (option --opt_level) |
For a very specific optimization, the optimizer may drop a volatile qualifier from a struct assignment. In some cases, the compiler may later perform an incorrect optimization, most commonly incorrectly reordering volatile assignments.
This bug can only happen in a function compiled with optimization level 1 or higher which contains both of the following: 1) A struct assign where the destination is volatile, and the source is a known constant, and the struct contains a bit-field, and the struct is of size "int" or smaller. 2) Any bit-field access (read or write) other than as part of a struct assign or initialization expression. That is, the name of the bit-field is present in the access expression. Note that the optimizer can create this situation by inlining functions, so 1 and 2 might be in different functions in the source code.
Consider a tree x = y where x and y are of type struct S. If the value of y is known at compile time (e.g. a const value), the optimizer will try to turn the struct constant into an integer constant (possibly combining bit-fields) and rewrite the tree to look like this: "(unsigned *)x = 32;" However, if y is volatile, that should be "*(volatile unsigned *)x = 32;" Because the access is not volatile, instruction scheduling could cause this instruction to drift past nearby volatile accesses. |
| CODEGEN-2050 |
Use of -o4 causes linker XML map file to have missing input_file entries |
Fixed |
ARM_16.9.0.LTS |
ARM_16.9.2.LTS |
|
|
| CODEGEN-2047 |
CMSIS Core v5 is not compliant with TI ARM Compiler |
Fixed |
ARM_16.9.0.LTS |
ARM_16.9.2.LTS |
The __INLINE macro in the TI compiler RTS linkage.h is no longer used and can be removed. |
CMSIS v5 defines the macro __INLINE, which interferes with the TI compiler RTS definition of the same macro in linkage.h. |
| CODEGEN-2025 |
Linker crash message incorrectly suggests submitting a preprocessed file |
Fixed |
ARM_16.9.0.LTS |
ARM_16.9.3.LTS |
|
|
| CODEGEN-2010 |
Decomp error involving packed class |
Fixed |
ARM_16.9.0.LTS |
ARM_16.9.2.LTS |
|
Fixed an issue that could result in a "Decomposition error" abort of the compiler. |
| CODEGEN-1976 |
Value of __cplusplus is wrong |
Fixed |
ARM_16.9.0.LTS |
ARM_16.9.2.LTS |
If possible, use the -ps or --strict_ansi options. This mode will use the strict definition of __cplusplus, which is 199711L. |
Our parser mimicked G++ behavior for the value of this macro in relaxed ANSI mode. This reproduced a bug in G++ versions v.4.7 and v.4.3 that has since been fixed. |
| CODEGEN-1703 |
Designated initializer plus struct hack hangs compiler |
Fixed |
ARM_16.9.0.LTS |
ARM_16.9.1.LTS |
Avoiding using string constants to initialize objects with flexible array members. Instead, use a brace-initialized array. For example:
struct { int a; char b[]; } mystruct = {0, {'h', 'e', 'l', 'l', 'o'} }; |
Fixed a compiler hang caused by initializing flexible array members with string constants.
struct {int a; char b[]; } mystruct = {0, "hello"} /* Would cause the compiler to hang and/or crash */ |
| CODEGEN-1640 |
MISRA 19.1 misreported: #include statements should only be preceded by other preprocessor directives |
Fixed |
ARM_16.9.0.LTS |
ARM_16.9.1.LTS |
No practical workaround |
|
| CODEGEN-1634 |
MISRA 7.1 misreported: octal tokens in token paste |
Fixed |
ARM_16.9.0.LTS |
ARM_16.9.1.LTS |
No practical workaround |
|
| CODEGEN-1632 |
MISRA 15.2 misreported: switch clause unconditional break |
Fixed |
ARM_16.9.0.LTS |
ARM_16.9.1.LTS |
Put an explicit break at the end of the compound statement |
|
| CODEGEN-1555 |
Incorrect result for ullong expression passed to abs |
Fixed |
ARM_16.9.0.LTS |
ARM_16.9.1.LTS |
Use llabs instead of abs |
abs(x-y) may compute an incorrect result when x and y are unsigned long long variables. |
| CODEGEN-1517 |
#pragma FUNCTION_OPTIONS meaningless unless at least -o0 is used |
Fixed |
|
ARM_16.9.0.LTS |
|
|
| CODEGEN-1429 |
Software pipelined loop generates different results than loop not pipelined |
Fixed |
ARM_16.9.0.LTS |
ARM_16.9.0.LTS |
Avoid unsigned expressions in subscripts or in computing subscripts, or compile with -o1 or -o0. |
|
| SDSCM00052814 |
TMS570LC4357 ECC algorithm not supported |
Fixed |
ARM_16.9.0.LTS |
ARM_16.9.1.LTS |
There is a backdoor in the implementation that you can use to realize this new algorithm. Use this algorithm specification:
ECC {
algo_name : address_mask = 0xffffffff
hamming_mask = /* address */
0x53aaa750, 0xeb45d688,
0xa6d54da8, 0x9e353c68,
0x7e0cfc18, 0xfe03fc00,
0x01fffc00, 0xfe0003f8,
/* upper */
0x2E4B2E4B, 0x57155715,
0x99A699A6, 0xE338E338,
0xFCC0FCC0, 0x00FF00FF,
0xFF0000FF, 0xFF0000FF,
/* lower */
0xD1B4D1B4, 0x57155715,
0x99A699A6, 0xE338E338,
0xFCC0FCC0, 0x00FF00FF,
0xFF0000FF, 0x00FFFF00,
parity_mask = 0x0c
mirroring = F021
}
If you value your sanity, do not ask where the constants come from. |
Some devices, such as TMS570LC4357 Hercules, have a FLASH bank in high memory, and ECC uses the high bits of the address in the ECC calculation. Therefore, we need to extend the participating address bits mask in the linker-generated ECC handling. |
| CODEGEN-1333 |
Structure assignment causes compiler to fail with INTERNAL ERROR: Decomposition error |
Fixed |
|
ARM_16.9.0.LTS |
Replace struct assignments involving packed structures with a memcpy() call to copy the contents of the RHS of the struct assign to the LHS. |
|
| CODEGEN-1312 |
RTS header errno.h no longer defines POSIX macros like EFAULT |
Fixed |
|
ARM_16.9.1.LTS |
|
|
| CODEGEN-1287 |
Compiler and documentation disagree on default for --enum_type |
Fixed |
|
ARM_16.9.0.LTS |
|
|
| SDSCM00040386 |
Remove -olength option from hex utility's help summary and Users Guides |
Fixed |
ARM_16.9.0.LTS |
ARM_16.9.0.LTS |
|
|
| SDSCM00052902 |
Assembler incorrectly issues error message: Address must be of a non-global defined in the current section |
Fixed |
|
ARM_16.9.0.LTS |
The suggested workaround is to go back to 15.12.3.LTS until the next ARM compiler release is available.
Alternately, alter the code such that the target label is a non-global symbol defined in the same section as the branch. If the symbol must be global, add a second non-global label such as fake_label and change the branch to "B fake_label". |
|
| SDSCM00052734 |
Internal error in trampoline generation when user defines data symbol named "signal" |
Fixed |
|
ARM_16.9.0.LTS |
It is a user error to have two different objects in the system with the same name. Rename one of the objects. |
|
| SDSCM00051485 |
Incorrect reordering of nested op= with ++ |
Fixed |
ARM_16.9.0.LTS |
ARM_16.9.0.LTS |
Don't embed "X op= Y++" under another assignment operator. |
An expression like "a += b += c++" will produce the wrong answer. The problem is specific to sub-expressions of the form "X op= Y++" that occur under another assignment operator. |
