| ID |
Summary |
State |
Reported In Release |
Target Release |
Workaround |
Release Notes |
| CODEGEN-2060 |
Even though option --buffer_diagnostics is not used, compiler issues diagnostic that says it is deprecated |
Fixed |
|
MSP430_17.3.0.STS |
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 |
|
MSP430_17.3.0.STS |
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 |
|
MSP430_17.3.0.STS |
|
|
| CODEGEN-2047 |
CMSIS Core v5 is not compliant with TI ARM Compiler |
Fixed |
|
MSP430_17.3.0.STS |
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-1976 |
Value of __cplusplus is wrong |
Fixed |
|
MSP430_17.3.0.STS |
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-1954 |
MSP430 manual incorrectly says MSP430X devices have no writeable memory above 64K |
Accepted |
|
MSP430_17.3.0.STS |
|
|
| CODEGEN-1705 |
Compiler documentation and RTS disagree on function names _TI_start_pprof_collection and _TI_stop_pprof_collection |
Fixed |
|
MSP430_16.12.0.STS |
|
|
| SDSCM00052878 |
Documentation error: #pragma pack should be lower case |
Fixed |
|
MSP430_16.12.0.STS |
|
|
| SDSCM00052904 |
Unsigned array index not truncated properly in array indexing expression |
Fixed |
|
MSP430_17.3.0.STS |
None |
An unsigned integer multiplication used in an array indexing expression was erroneously optimized into instructions performed in 20 bits instead of 16 bits, thereby failing to truncate an overflowed value into zero. |
