mcu_18.1_closed_defects

ID Summary State Reported In Release Target Release Workaround Release Notes
CODEGEN-3918 Writing multiple input sections in one line unexpectedly changes how input sections are combined into output sections Fixed C2000_15.12.0.LTS, C2000_16.9.0.LTS, C2000_18.1.0.LTS C2000_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 C2000_15.12.0.LTS, C2000_16.9.0.LTS, C2000_17.9.0.STS C2000_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 C2000_17.9.0.STS, C2000_15.12.6.LTS, C2000_16.9.4.LTS C2000_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-3795 C2000 compiler fails to emit load DP instruction Fixed C2000_16.9.0.LTS, C2000_17.6.0.STS, C2000_18.1.0.LTS C2000_18.1.0.LTS Use compiler option --disable_dp_load_opt to disable DP load optimization. The compiler fails to update the DP register before certain variable accesses. The issue is likely to occur when accessing variables that belong to sections that contain a combination of blocked and unblocked variables.
CODEGEN-3676 CLA store-load cycles for read-before-write pipeline hazard Fixed C2000_17.6.0.STS C2000_17.9.0.STS No work around other than upgrade to a fixed version. For CLA instruction scheduling of stores followed by loads, only 2 cycles (instead of 3 cycles) were placed between the store/load. Fixed this to be the 3 cycles required by CLA pipeline to avoid read-before-write issue. To offset code size impact (increased NOPs), enabled better memory disambiguation checking to additionally eliminate unnecessary NOPs if a store/load pair were to different memory locations.
CODEGEN-3655 Incorrect code generated for multiplication Fixed C2000_15.12.0.LTS, C2000_16.9.0.LTS, C2000_17.9.0.STS C2000_18.1.0.LTS Under a set of special circumstances too detailed for this release note to describe, it is possible for the compiler to drop certain multiply instructions, yielding incorrect code. The circumstances are somewhat rare. This will probably only happen with multiplications near an access of a 32-bit variable that is cast to 16 bits.
CODEGEN-3619 pragma triggers false MISRA-C:2004 19.1/A warning Fixed C2000_15.12.0.LTS, C2000_16.9.0.LTS, C2000_17.9.0.STS C2000_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 C2000_15.12.0.LTS, C2000_16.9.0.LTS, C2000_17.6.0.STS C2000_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-3580 C2000 float to int intrinsics matching error Fixed C2000_15.12.0.LTS, C2000_6.4.0B1, C2000_16.9.0.LTS, C2000_16.12.0.STS C2000_17.9.0.STS Assign the result to the same signedness as the conversion and subsequently cast it to the other: unsigned int x = __f32toui16r(f); int y = x; int y = __f32toi16r(f); unsigned int x = y; The following intrinsics fail to match depending on whether the result is assigned to a signed or unsigned int. Conversion to unsigned int fails to match when assigned to signed int: int x = __f32toui16r(f); Conversion to signed int fails to match when assigned to unsigned int: unsigned y = __f32toi16r(f);
CODEGEN-2373 Internal linker error triggered by function alias Fixed C2000_15.12.0.LTS, C2000_16.9.0.LTS, C2000_17.9.0.STS C2000_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 C2000_17.6.0.STS C2000_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 C2000_17.6.0.STS C2000_17.9.0.STS Add quotes around argument to offending 'echo' command in lib/src/Makefile of the tool's installation.
CODEGEN-2343 C2000 indexed addressing performance degradation Fixed C2000_15.12.0.LTS, C2000_16.9.0.LTS, C2000_17.6.0.STS C2000_17.9.0.STS For array indexing expressions of the form P[N] or P->f, whether written by the user or generated by an optimization, where N is a constant larger than 255 (after scaling by the size of the type), the compiler may generate inefficient code. We want this: MOV AR0, #N MOVL ... *AR1[AR0] However, the compiler was actually doing this: MOV ACC, AR1 ADD ACC, #(N/2) << 1 MOV AR2, ACC MOVL ..., *AR2[0] This is much more costly
CODEGEN-2286 palign(8) of .init_array messes up __TI_INITARRAY_Limit address Fixed C2000_15.12.0.LTS, C2000_16.9.0.LTS, C2000_17.9.0.STS C2000_17.9.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-2182 INTERNAL ERROR: opt2000 experienced a segmentation fault Fixed C2000_15.12.0.LTS, C2000_16.9.0.LTS, C2000_17.3.0.STS C2000_17.6.0.STS The problem appears with a while-loop that places the increment or decrement ahead of the MAC. Work around it by using a for-loop, or by moving the increment/decrement to the end of the loop body (instead of in the while-loop predicate, for instance). A while-loop like while (n--) sum += *x++ * *y++; may cause the compiler to crash. Use a for-loop instead.
CODEGEN-2179 I16TOF32 or UI16TOF32 lost or cannot be generated Fixed C2000_15.12.0.LTS, C2000_16.9.0.LTS, C2000_17.3.0.STS C2000_17.6.0.STS The compiler incorrectly modeled I16TOF32 and UI16TOF32. This had two detrimental effects: 1. If the compiler created one of these instructions with a memory operand and gave it post-increment addressing, it could be dropped as dead code, leading to incorrect results. 2. Some loops that should have used one of these instructions would instead sign extend the 16-bit integer and used I32TOF32 or UI32TOF32 instead.
CODEGEN-2176 RPTB block containing RPT is too small Fixed C2000_15.12.0.LTS, C2000_16.9.0.LTS, C2000_17.3.0.STS C2000_17.6.0.STS This bug can occur when there is a small loop containing a smaller loop, where the smaller loop behaves like memset(foo, 0, n). Only the fill value zero will trigger this bug. The generated RPTB may be one byte too small to be legal, and the assembler will reject the RPTB.
CODEGEN-2171 C2000 compiler disables if conversion on mac Fixed C2000_15.12.0.LTS, C2000_16.9.0.LTS C2000_17.6.0.STS
CODEGEN-2168 Incorrect use of MPYA overwrites T register, resulting in wrong computation Fixed C2000_15.12.0.LTS, C2000_16.9.0.LTS, C2000_17.6.0.STS C2000_17.6.0.STS The kill of register T was not being captured in the MPYA P,loc16,#16bit instruction causing a prior load to the T register to be erroneously overwritten by a subsequent MPYA P,loc16,#16bit instruction.
CODEGEN-2166 INTERNAL ERROR: lnk2000 failed to allocate memory Fixed C2000_15.12.0.LTS, C2000_16.9.0.LTS, C2000_17.3.0.STS C2000_17.6.0.STS Compile with --disable:cla_scratchpad_overlay, or do not allow CLA functions to call any function in any section that may contain its own ancestor. CLA modules should have each function in its own text section, and CLA functions should absolutely not be recursive or mutually recursive in any way. For this test case, hand-coded CLA functions had two functions (A and C) in the same text section. A has a call to B, which is in a different text section. B has a call to C. This forms a cycle in the call graph, because the linker can only see sections and doesn't realize A and C are different functions. Due to a bug in the CLA scratchpad overlay optimization, this cycle would cause the linker to go into an infinite loop.
CODEGEN-2119 Stack usage assistant call graph misses callee relationship for some direct calls Fixed C2000_15.12.0.LTS, C2000_16.9.0.LTS, C2000_17.6.0.STS C2000_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 C2000_15.12.0.LTS, C2000_16.9.0.LTS, C2000_17.6.0.STS C2000_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 C2000_15.12.0.LTS, C2000_16.9.0.LTS, C2000_17.3.0.STS C2000_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 C2000_16.9.0.LTS, C2000_16.12.0.STS C2000_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 C2000_15.12.3.LTS, C2000_6.4.0B1, C2000_16.9.0.LTS, C2000_16.12.0.STS C2000_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 C2000_15.12.0.LTS, C2000_16.9.0.LTS, C2000_16.12.0.STS C2000_17.3.0.STS
CODEGEN-1979 Statements before declarations with no white space (aggravated by macros) may cause incorrect parser error Fixed C2000_15.12.0.LTS, C2000_16.9.0.LTS, C2000_17.6.0.STS C2000_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 C2000_15.12.0.LTS, C2000_6.4.0B1, C2000_16.9.0.LTS, C2000_16.12.0.STS C2000_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-1974 Remove --symdebug:coff from the compiler manual Fixed C2000_16.9.1.LTS C2000_17.3.0.STS
CODEGEN-1710 Illegal instruction selection for __byte_peripheral_32 on FPU32 Fixed C2000_15.12.0.LTS, C2000_16.9.0.LTS, C2000_16.12.0.STS C2000_17.3.0.STS Try a lower level of optimization. For our test case, optimization levels lower than 3 did not expose the bug. However, this workaround may not help for all test cases. Although byte peripheral types are integral, when FPU32 device support is enabled, the compiler might store 32-bit integral values in floating point registers when CPU registers are unavailable. The compiler erroneously generates a MOVL instruction instead of a MOV32 instruction for moving 32-bit byte peripheral data between floating point registers and byte peripheral memory, if this data gets assigned to a floating point register.
CODEGEN-1709 Using #pragma INTERRUPT(HPI) crashes the compiler Fixed C2000_15.12.0.LTS, C2000_6.4.0B1, C2000_16.9.0.LTS, C2000_16.12.0.STS C2000_16.12.0.STS Besides not using #pragma INTERRUPT(HPI), there is no workaround. The compiler requires an update. Fixed a crash that occurs when using #pragma INTERRUPT(HPI)
CODEGEN-1705 Compiler documentation and RTS disagree on function names _TI_start_pprof_collection and _TI_stop_pprof_collection Fixed C2000_16.12.0.STS
CODEGEN-1656 Using --gen_profile_info does not work with -o4 Fixed C2000_15.12.0.LTS, C2000_16.9.0.LTS, C2000_17.6.0.STS C2000_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.
CODEGEN-1329 Lower diagnostic about redefined opcode to a warning, when a compiler intrinsic is redefined Fixed C2000_15.12.0.LTS, C2000_16.9.0.LTS, C2000_16.12.0.STS C2000_17.3.0.STS Remove the #define or do not include the header file in assembly files. When a header file attempting to redefine an opcode name is included in assembly files, the assembler issues an error because it is not legal to redefine an opcode name. While this behavior is correct, it causes programs to fail to compile when some C2000 header files are included in assembly files due to the "#define eallow ..." in the header files.
SDSCM00051734 Accepts invalid CLA instruction "MMOV32 MRx, MSTF" Fixed C2000_15.12.0.LTS, C2000_16.9.0.LTS, C2000_17.9.0.STS C2000_18.1.0.LTS When coding in assembly for the CLA, the assembler accepts an instruction of the form MMOV32 MRx, MSTF. This is not a valid instruction.
SDSCM00050540 Accepts invalid CLA instruction "MMOV32 mem, MRn, COND" Fixed C2000_15.12.0.LTS, C2000_16.9.0.LTS, C2000_17.9.0.STS C2000_18.1.0.LTS Care should be taken when writing hand-coded assembly to only write valid instructions as they are documented. The CLA assembler accepts an instruction of the form "MMOV32 mem, MRn, COND", which is not legal. There is no conditional MMOV32 to a memory destination. The only valid conditional MMOV32 instructions have register (MRn) destinations.
SDSCM00043877 Emit error message when objects of size 512MB or larger truncated Fixed C2000_16.9.0.LTS, C2000_17.9.0.STS C2000_18.1.0.LTS N/A Due to an internal limitation, the code generation tools cannot presently allocate objects of size 512 MB or larger. When such objects are declared in the code, they were silently truncated and compilation continued without any diagnostics.

Generated on Fri Jan 26 12:30:55 2018