| CODEGEN-3918 |
Writing multiple input sections in one line unexpectedly changes how input sections are combined into output sections |
Fixed |
MSP430_15.12.0.LTS, MSP430_16.9.0.LTS, MSP430_18.1.0.LTS |
MSP430_18.1.0.LTS |
Stick with separate lines, if there are subsection cases like this one that should be comprehended. |
In a linker command file, using a line like "hello.obj (.const, .far)" may link differently than two lines with one section each. The problem is that the single line is interpreted as the OR of the two sections, and the linker does not understand that the OR also encompasses any of their subsections. Two separate lines are analysed separately and completely. |
| CODEGEN-3858 |
OFD gets DIE attribute offset wrong when using --dwarf_display=none,dinfo |
Fixed |
MSP430_15.12.0.LTS, MSP430_16.9.0.LTS, MSP430_17.9.0.STS |
MSP430_18.1.0.LTS |
If you use --dwarf_display=none,dinfo, use --dwarf_display=none,dinfo,types instead |
You can use OFD to display the DWARF debugging information in your object files by using the option '--dwarf' (or -g). You can narrow the categories of DWARF information displayed by using the '--dwarf_display' option. If you use the option --dwarf_display=none,dinfo you will see the DWARF DIE objects in the .dwarf_info section, but you will not see any DW_AT_type attributes unless you also use the "types" flag. This is not a bug. However, when OFD skips a DW_AT_type attribute, it displays the offset of the skipped DW_AT_type for the next attribute instead of the next attribute's correct offset. |
| CODEGEN-3801 |
Linker crashes with INTERNAL ERROR (unhandled exception) |
Fixed |
MSP430_17.9.0.STS, MSP430_15.12.6.LTS, MSP430_16.9.4.LTS |
MSP430_18.1.0.LTS |
|
The linker experiences a segmentation fault when there is a reference from a debug section to a symbol without a section (for example, an absolute symbol). |
| CODEGEN-3619 |
pragma triggers false MISRA-C:2004 19.1/A warning |
Fixed |
MSP430_15.12.0.LTS, MSP430_16.9.0.LTS, MSP430_17.9.0.STS |
MSP430_18.1.0.LTS |
N/A |
Certain pragmas appearing prior to #include statements, such as #pragma RESET_MISRA, would cause MISRA warning 19.1/A to be issued:
MISRA-C:2004 19.1/A: #include statements in a file should only be preceded by other preprocessor directives or comments |
| CODEGEN-3597 |
ELF header field e_phoff should be 0 when no program header is present |
Fixed |
MSP430_15.12.0.LTS, MSP430_16.9.0.LTS, MSP430_17.6.0.STS |
MSP430_17.9.0.STS |
|
ELF header field e_phoff should be 0 when no program header is present, and ELF header field e_shoff should be 0 when no section headers are present. |
| CODEGEN-2424 |
Update mpu_init.c file for FR57xx family MPU in TI CGT |
Fixed |
MSP430_17.9.0.STS, MSP430_16.9.6.LTS, MSP430_15.12.7.LTS |
MSP430_17.9.0.STS |
Upgrade to MSP430 compiler version 17.9.0.STS, or 16.9.6.LTS, or 15.12.7.LTS.
Or rebuild your compiler RTS after adding below lines to mpu_init.c:
extern volatile unsigned char MPUCTL0_H;
Add below to the end of __mpu_init() routine definition:
MPUCTL0_H = 0x0; /* Lock MPU */ |
The current Run Time System (RTS) definition of __mpu_init() in mpu_init.c does not enable MPU protection after initialization. The RTS implementation only applies to FR57xx devices. |
| CODEGEN-2373 |
Internal linker error triggered by function alias |
Fixed |
MSP430_15.12.0.LTS, MSP430_16.9.0.LTS, MSP430_17.9.0.STS |
MSP430_18.1.0.LTS |
|
Linker sometimes generates "Assertion failed" message and aborts. |
| CODEGEN-2372 |
C2000 hex utility emits spurious warning about creating an extra output file |
Fixed |
MSP430_17.6.0.STS |
MSP430_17.9.0.STS |
Ignore the warning or suppress it with option --diag_suppress=21117. |
The Hex utility sometimes emits spurious warnings about writing data to auto-generated files. |
| CODEGEN-2371 |
Compiler library automatic build with mklib fails |
Fixed |
MSP430_17.6.0.STS |
MSP430_17.9.0.STS |
Add quotes around argument to offending 'echo' command in lib/src/Makefile of the tool's installation. |
|
| CODEGEN-2286 |
palign(8) of .init_array messes up __TI_INITARRAY_Limit address |
Fixed |
MSP430_15.12.0.LTS, MSP430_16.9.0.LTS, MSP430_17.9.0.STS |
MSP430_17.3.0.STS |
In the linker command file, replace
.init_array > FLASH, palign(8), fill = 0xffffffff
with the following GROUP statement:
GROUP
{
.init_array
} > FLASH, palign(8)
The palign(8) on GROUP will ensure that any required padding is added after .init_array. However, both the size of .init_array and the value of __TI_INITARRAY_Limit remain unchanged. |
Applying palign(8) to .init_array caused __TI_INIT_ARRAY_Limit to be set to the end of .init_array including the padding. This broke RTS startup code responsible for calling constructors because the table of constructors now includes invalid data. This bug has been fixed and __TI_INIT_ARRAY_Limit is no longer affected by padding. |
| CODEGEN-2119 |
Stack usage assistant call graph misses callee relationship for some direct calls |
Fixed |
MSP430_15.12.0.LTS, MSP430_16.9.0.LTS, MSP430_17.6.0.STS |
MSP430_17.6.0.STS |
|
The Object File Display utility failed to detect function callees when generating call graph information for functions that contain nested blocks. |
| CODEGEN-2113 |
Hex utility mishandles space in directory name of output file |
Fixed |
MSP430_15.12.0.LTS, MSP430_16.9.0.LTS, MSP430_17.6.0.STS |
MSP430_17.6.0.STS |
Use directory names without spaces for output files. |
The hex utility did not correctly handle spaces in output directory and file names. |
| CODEGEN-2098 |
Temp filename collisions on Windows with many parallel invocations |
Fixed |
MSP430_15.12.0.LTS, MSP430_16.9.0.LTS, MSP430_17.3.0.STS |
MSP430_17.6.0.STS |
|
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 |
MSP430_16.9.0.LTS, MSP430_16.12.0.STS |
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_15.12.0.LTS, MSP430_16.9.0.LTS, MSP430_16.12.0.STS |
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_15.12.0.LTS, MSP430_16.9.0.LTS, MSP430_16.12.0.STS |
MSP430_17.3.0.STS |
|
|
| CODEGEN-2047 |
CMSIS Core v5 is not compliant with TI ARM Compiler |
Fixed |
MSP430_15.12.0.LTS, MSP430_16.9.0.LTS, MSP430_16.12.0.STS |
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-1995 |
Pointer math addend incorrectly truncated to ptrdiff_t on MSP430 |
Fixed |
MSP430_15.12.0.LTS, MSP430_16.9.0.LTS, MSP430_17.6.0.STS |
MSP430_17.9.0.STS |
|
The compiler was incorrectly handling array index expressions where the value of the index expression did not fit in ptrdiff_t. In some cases, the compiler would truncate the value to ptrdiff_t, changing the value. This bug can only occur in restricted or large data models.
This fix can affect the compiler's ability to optimize code. Importantly, for restricted data model, the compiler can no longer assume that pointer index expressions can use indexed addressing mode. Indexed addressing mode has a 16-bit signed offset, which may not be big enough to hold the value of the index expression. In this case, the pointer index expression must be carried out as pointer arithmetic followed by a non-indexed addressing mode, which requires more instructions and thus more cycles. This means that in restricted data model, there may be a performance loss when upgrading to this version.
Whether this loss occurs, and how big the loss is, depends greatly on whether your program uses pointer index expressions in critical loop bodies. We have observed that most of our benchmarks are unaffected, but we have some benchmarks that degraded after this fix. |
| CODEGEN-1979 |
Statements before declarations with no white space (aggravated by macros) may cause incorrect parser error |
Fixed |
MSP430_15.12.0.LTS, MSP430_16.9.0.LTS, MSP430_17.6.0.STS |
MSP430_18.1.0.LTS |
Do not start any statement in the left-most column
Rearrange your code so that there are no statements before declarations. |
C99 and C++ allow statements before declarations in functions. This is not allowed by the C89 language, but as an extension, the TI compiler allows such statements in relaxed mode. However, in certain circumstances, the compiler may emit the 'error: expected "}"' for otherwise legal code which has statements before declarations.
This problem can only occur in relaxed C89 mode (which is the default mode), and 1) you have a function with statements that start in the left-most column, or 2) you use macros where the macro body contains C code with statements before declarations. |
| CODEGEN-1976 |
Value of __cplusplus is wrong |
Fixed |
MSP430_15.12.0.LTS, MSP430_4.4.0B1, MSP430_16.9.0.LTS, MSP430_16.12.0.STS |
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 |
Fixed |
MSP430_16.9.1.LTS |
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 |
|
|
| CODEGEN-1656 |
Using --gen_profile_info does not work with -o4 |
Fixed |
MSP430_15.12.0.LTS, MSP430_16.9.0.LTS, MSP430_17.6.0.STS |
MSP430_17.6.0.STS |
Lower the optimization level to -o3. |
Previously, link time optimization failed when profiling options --gen_profile_info and use_profile_info were specified in combination with the --opt_level=4 option. The errors were because profiling options were not supported when used in combination with --opt_level=4.
Application profiling during whole program optimization is now supported. Profiling options --gen_profile_info and --use_profile_info may now be combined with --opt_level=4. |
| 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_15.12.0.LTS, MSP430_16.9.0.LTS, MSP430_16.12.0.STS |
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. |
