| ID |
Summary |
State |
Reported In Release |
Target Release |
Workaround |
Release Notes |
| CODEGEN-6289 |
Pointer to VLA 2D array computation in IF condition is double-adjusted and garbled |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.7.LTS |
Given "if (p[i][j])", moving the access into a temp with "T = p[i][j]; if (T)" is the simplest workaround. Since the bug happens early in compilation, optimisation level doesn't matter.
Recasting the IF as a quest/colon, if feasible, is also a workaround. |
A variable-length-array access for an array of at least two dimensions, if used in the predicate of an IF statement, may be mishandled and refer to an incorrect element, possibly outside the array. |
| CODEGEN-6132 |
pdd tool fails when program includes unused file |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.7.LTS |
Leaving the sys_pcr.obj file out of the link command works, but it's hard to tell that that's the problem file. |
The profile decoder, armpdd or pdd2000 or pdd430 or pdd6x, may fail when the program on which it is called includes a file whose functions are not included in the link.
In the test case given, the file sys_pcr.obj contains functions that are not called anywhere and therefore are not included in the .out file. However, due to some quirk that we have not yet isolated, the debug info for sys_pcr.obj *is* included. When the profile decoder collects its data, it uses the debug info to locate it; the faulty extra debug info points to invalid locations, causing the warnings.
We don't know yet whether the problem is with a single excluded function, more than one, or a whole file whose functions aren't included. What we have done is to make the profile decoder recognise and ignore the bogus debug info. |
| CODEGEN-6130 |
deque push_back of structure larger than 64-bytes tries to write to invalid memory location |
Fixed |
MSP430_18.1.1.LTS |
MSP430_18.1.7.LTS |
1. Keep deque elements to 64 bytes or less.
2. Edit include/libcxx/deque and change the definition of "value" in "__deque_block_size" to an expression that is never less than 2.
3. Use a different data structure. |
The implementation of std::deque in libc++ has a bug when the block size is 1. The stock version never uses a size that small and never exposes the bug. The TI version, used for ARM and MSP430 since 18.1.1.LTS and C6000 since 8.3.0, uses a formula that makes the block size 1 when the deque's elements are 65 bytes or larger. (Our parts are generally used in embedded situations and often have limited memory.) |
| CODEGEN-5843 |
Use of --check_misra=14.10 causes non-MISRA related warning to be emitted |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.7.LTS |
No direct workaround. The warning can be suppressed by the usual methods, or corrected as described in the report. |
If a local variable's address is taken before the variable is initialised, there will usually not be a warning with default settings. However, if any --check_misra option is used, the compiler will issue a used-before-set warning for the variable. |
| CODEGEN-5563 |
Checking for MISRA rule 20.1 causes macro redefinition to be ignored |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.7.LTS |
None. To detect redefined macros that aren't predefined, --check_misra=20.1 must not be in the compilation options. |
The --check_misra=20.1 option, which looks for redefined reserved identifiers such as predefined macros, will accidentally suppress warnings about redefinitions of macros that *aren't* predefined. Since those aren't included in the group that 20.1 tests for, no warning will be issued at all. |
| CODEGEN-5533 |
Loop with Cortex-R, -mf3, and DWARF debug leads to assembler error "defined differently in each pass" |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.7.LTS |
Several pieces have to come together for this problem to happen.
--opt_for_speed needs to be 3 or greater; thus a workaround is to reduce optimization to --opt_for_speed=1.
The source code has to have one or more IFs, followed by a nested scope that isn't part of a compound statement and defines local variables, followed by a loop. Another workaround is thus to move the local variable definitions to the enclosing scope. (Another that works for the given test case but isn't necessarily general is to initialise all those local variables, where they're defined in the nested scope.)
Normal debug info must be present; a final workaround is therefore to use --symdebug:none to suppress debug info. Of course, that makes debugging difficult. |
The assembler will become confused when presented with the sequence of a .align, an instruction that is smaller than the specified alignment, a label, and the DWARF DW_AT_low_pc directive. Because of the way it processes alignments and labels in different passes, it will conclude that the label was defined with two different values, and report an error.
This sequence is not something a human asm programmer would write. It arises from compiling a particular shape of statements in a loop, with a particular set of compilation options, to position the label and the .align and the directive. See the Workaround, which also indicates how to modify the code or compiler options to avoid this bug. |
| CODEGEN-5333 |
Emit error message when referenced placeholder routine not selected during specialization |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.7.LTS |
|
Boot routine specialization support was added in CGT v18.1.0.LTS. In the case that a specialized boot routine was intended to be used but no suitable routines were found, the linker would fail to issue an error and complete linking the code without the required routine. The program would then fail during run time. Now the linker will issue an error. |
| CODEGEN-6135 |
Using --opt_level=4 with inconsistent --near_data can cause relocation overflow error |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.6.LTS |
Make sure that all files are compiled with --near_data=none when making a global variable that must use large data pointers, or else use -O3 instead of -O4. |
This test case has a large global array, which requires --near_data=none, and indeed the files that reference it have that option. However, another file (mpu_init.c) was compiled with --near_data=globals. Due to a bug in the compiler, all the --near_data options are merged at -O4 into a single --near_data that applies to all the recompiled files, and the merged value is "globals."
With --near_data=globals, short pointers are used for the large global array, which can't work and causes a relocation-overflow error. The solution to the compiler bug is to stick with the original --near_data for each file. The workaround for this case is to make sure all files are compiled with --near_data=none, or else to use -O3 instead of -O4. |
| CODEGEN-5986 |
Compiler may crash when auto as return type of uninstantiated member function in template class resolves to template paramet |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.6.LTS |
Avoid "auto" as the return type of a member function if its immediate resolution is a template parameter.
Or explicitly instantiate the class or function. In the given test case, there's a variable defined with type EventSubscriberTable<int>. To avoid the problem, then, include either
template class EventSubscriberTable<int>;
or
template auto EventSubscriberTable<int>::getBroadcastList(void);
in the source file. |
Given a class definition like
template <typename T>
class Table {
public :
auto getList(void) { return m_Callbacks; }
private :
T m_Callbacks;
};
where the member function getList() returns "auto" and that "auto" can be seen to be "T", and this program:
int main(int argc, char* argv[])
{
Table<int> m_Table;
return 0;
}
in which the Table class is instantiated but the function getList() is never used, the compiler may crash.
The problem requires the combination of auto, template parameter, and uninstantiated function. Changing any of those details will avoid it. |
| CODEGEN-5943 |
Compiler may lose volatile qualifier in A->B->C when B and C are both volatile |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.6.LTS |
The expression has to contain both dereferences, eg, a->b->c, for the problem to appear. If they're separated by using a temp, as in
T * volatile p;
p = a->b;
... p->c ...
then the problem should be avoided. Making the temp "p" volatile is also important, to prevent the compiler from recombining the two dereferences.
Or compile with -o1, -o0, or -ooff. |
In an expression like A->B->C, when B and C are both volatile structure fields, we'd expect to see two distinct memory accesses every time. There is a bug in the compiler specifically with having two dereferences in a single expression, ie, A->B->C, in which it may lose the volatile qualifier from B. That may lead it to save A->B in a temporary variable and reuse that value instead of re-reading it as is supposed to happen. |
| CODEGEN-5905 |
Linker command file option --define with pathname with many directory components leads to error: "source line too long" |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.6.LTS |
|
|
| CODEGEN-5809 |
MSP430 compiler may intermittently crash when using hardware multiply |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.6.LTS |
Don't use the hardware multiply, ie, --use_hw_mpy=none. |
The MSP430 compiler may crash when using the hardware multiply, eg, --use_hw_mpy=F5. There is not a simple code sequence that triggers the problem; the right combination of instructions and codegen passes may access outside the bounds of an internal compiler structure, and that may trigger a crash. |
| CODEGEN-5791 |
C++ enum class with explicit type has some problems |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.6.LTS |
Avoid specifying an explicit base type for an enum. |
Values of a C++ enum class type with an explicit base type may not be cast properly to and from integral types. The exact conditions depend on undefined behavior, and thus are not 100% predictable; the known cases happen only on Windows, though the compiler uses the same codebase on all platforms. |
| CODEGEN-5674 |
Under -o4, compiler may assume a global variable is constant, if it's only set in files containing inline asm() |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.6.LTS |
First, compiling with -o3 (or less) instead of -o4 will avoid the problem.
Second, making g_sys_opmode volatile does indeed work around the problem. Since the "volatile" qualifier tells the compiler that something is modifying the variable outside the compiler's view, that's exactly what is needed to keep it from being assumed constant.
Third, removing the asm() from main.c will work around the problem, by including main.c in the recompilation. I modified EINT/DINT and EALLOW/EDIS macros in F2806x_Device.h and two cpu.h files, making them use the intrinsics __enable_interrupts, __disable_interrupts, __eallow, and __edis. As it happens, __enable_interrupts and __disable_interrupts control both INTM and DBGM, while the macros control them individually, so this may not be a completely satisfactory solution. |
The immediate trigger for the bug is that main.c contains asm() statements. That's the only file that sets g_sys_opmode; other files only read it. The presence of asm() keeps the file out of the recompilation that -O4 does. The compiler, however, still thinks it has the whole program (or at least the important parts); since it doesn't see main.c, it doesn't see the writes, and concludes that g_sys_opmode is a constant 0. |
| CODEGEN-5623 |
Makefile dependence generation (--preproc_dependency) should quote spaces in filenames |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.6.LTS |
Rename the files so that they don't have spaces in the names. |
The parser generates makefile dependencies with the --preproc_dependency option. However, if any filename has a space in its name, the makefile dependencies will not be formatted in a way that can be parsed by make. |
| CODEGEN-5578 |
Compiler may crash when using attribute cc_rom |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.5.LTS |
Make sure the return value is used. Test the return value, or assign it to a dummy volatile variable. |
When calling a cc_rom function that returns an int8_t value, the compiler may crash if the return value is ignored. |
| CODEGEN-5574 |
Loop controlled by unsigned char counter iterates more than 255 times |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.6.LTS |
Compile at -o1 or less, or restructure the loop to make it not need the 8-bit wraparound. |
A do-while loop with an unsigned loop variable narrower than int can miss one of its wraparound cases, for instance if the loop counts down and the counter starts at zero. The compiler may promote the variable to int, making it wider than the original and thus it will experience a much larger count when it wraps. |
| CODEGEN-5560 |
ULP warning crashes compiler while compiling C++ file |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.5.LTS |
Remove the option --advice:power=all
|
When using the ULP option --advice:power=all with C++ code, the compiler may crash while trying to print the name of a C++ member function. |
| CODEGEN-5558 |
C++14 enum class values in a switch causes no match for MINUS |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.5.LTS |
|
|
| CODEGEN-5527 |
Local structure initialization is incorrectly optimized away |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.6.LTS |
None better than the one given in the description. |
A program that saves the address of a variable in an initialised local struct, but does not use the variable directly, may lose the part of the struct that saves the address. |
| CODEGEN-5511 |
Compilers other than C6000 mistakenly support option --legacy |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.6.LTS |
|
|
| CODEGEN-5486 |
Global constexpr class errors out when assigning to member data |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.6.LTS |
The error can be avoided If the constexpr class definition is wrapped in a function which simply returns the instance of the class.
For example:
constexpr MyClass getA()
{ MyClass A("This is a constant literal"); return A;}
Using 'getA()' instead of 'A' will work as expected. |
Constexpr class definitions may generate spurious parser errors, including one about "accessing expired storage." |
| CODEGEN-5403 |
Improve documentation in Compiler Guides for PERSISTENT and NOINIT pragmas |
Fixed |
MSP430_18.1.3.LTS |
MSP430_18.12.0.LTS |
|
|
| CODEGEN-5317 |
Ternary (?:) expression with 0/1 result uses type of predicate, not result, when optimised |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.4.LTS |
Compile with -Ooff. |
An expression like "(p ? 1 : 0)" can be converted by the compiler into "(p != 0)". If the types of 1 and 0 are wider than int, and the expression is shifted left, as in "(p ? 1UL : 0UL) << 16", then the value shifted will be int instead of the wider type, and the overall value will be incorrect. |
| CODEGEN-5236 |
Register allocation failure |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.4.LTS |
No practical workaround |
The compiler may, in rare cases, allocate registers incorrectly. The most common symptom would be an internal error indicating that register allocation has failed. This problem has only been observed on C28x compiler version 8.1.3.LTS, but could occur for other ISAs. |
| CODEGEN-5187 |
Compiler mishandles signed right-shifts by 16 on targets with 16-bit ints |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.5.LTS |
None known. |
For MSP430 and C2000, a right-shift of a signed long (ie, 32-bit) expression by 16 -- X>>16 -- will be compiled as an unsigned right-shift, which can lead to incorrect sign-extensions in the result. |
| CODEGEN-5119 |
Using #pragma RETAIN does not keep a static file level variable |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.6.LTS |
Use both "#pragma RETAIN" and "__attribute__((used))" at the same time. |
The RETAIN pragma may not keep an unused variable like it's supposed to. |
| CODEGEN-5033 |
Functions in <string> incorrectly return NULL |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.4.LTS |
Ignore or suppress the warning. |
char_traits<char>::find() and char_traits<wchar_t>::find() return char* and wchar_t*, respectively. In our __string file (included by <string>), they are written to return NULL, which is (void*)0 and not the same type as the declaration, thus producing a warning. We have updated the file to make them return 0, which fixes the warnings. |
| CODEGEN-4959 |
Premature deallocation of VLA arrays |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.4.LTS |
Rewrite the code so that it does not use VLA |
The intent behind C99 variable-length arrays (VLA) is that they are allocated on the stack, and thus are deallocated when the call frame is inactivated (by returning, or by being discarded with longjmp). However, we don't support actually allocating them on the stack, so we use malloc/free to simulate this. This works fine if the function exits normally; the parser turns a VLA declaration into a call to __vla_alloc, and placing a __vla_dealloc just before the function exits. However, what do you do if a longjmp skips over the function exit? The implementation needs a way to detect that and clean up dead VLAs.
It does this by keeping track of the SP during the call to __vla_alloc. When either __vla_alloc or __vla_dealloc is called, it looks at its own SP and compares it to the stored SP for each of the allocated VLAs it knows about. For MSP430, the stack grows toward zero. If the SP for any of the known VLAs is less than the current function's SP, those VLAs were allocated by a call to __vla_alloc deeper in the call stack than the current function, and thus must be dead.
This fails when procedure abstraction (PA) is involved, because PA creates a tiny little function to contain the PA code. This tiny little function has a lesser SP than the calling function, so it looks like a call deeper in the call stack. If there are any calls to __vla_alloc in the PA code, and any calls to either __vla_alloc or __vla_dealloc left in the calling function, the latter will cause any VLAs allocated in the PA code to be freed prematurely.
|
| CODEGEN-4931 |
Applying __attribute__((used)) to static variable does not work |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.6.LTS |
|
|
| CODEGEN-4885 |
See MISRA diagnostics when compiling stdio.h |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.5.LTS |
none |
A program that includes <stdio.h> and checks for MISRA warnings may see some from stdio.h itself, which should not happen. |
| CODEGEN-4700 |
Incorrect diagnostic when using macro that comes from macro library |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.5.LTS |
Unpack all of the macro libraries and re-pack them into a single unified library, or rename all macros to names with less than 15 characters |
If you are using assembler macro libraries, and you have more than one library, and two or more of those libraries have macros with names that are longer than 15 characters, you may get an incorrect error message from the assembler saying "Bad archive entry" |
| CODEGEN-4678 |
Incorrect error due to typedef of very large object |
Fixed |
|
MSP430_18.1.3.LTS |
As a workaround, remove the typedef. Where the typedef was used, instead use the type the typedef refers to. |
The TI compiler infrastructure is incapable of handling user-declared objects above a certain size, because it mistakenly truncates the size of very large objects. Formerly, this resulted in quiet corruption, which was defect CODEGEN-449. Now that CODEGEN-449 is fixed, the compiler will emit an error if the user attempts to create a type larger than the tool can handle. However, this error check is not quite right for typedefs. A typedef for a very large object that is still within the compiler's limit may cause the parser to mistakenly emit an error that the object is greater than the maximum supported size. |
| CODEGEN-4638 |
When shift counts are higher than 32, compiler sometimes optimizes to an incorrect shift count |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.2.LTS |
Turn off optimization by using optimization level off.
Otherwise, avoid a left-shift by a constant as an operand of the listed operations. However, compiler optimizations could interfere with this. Try keeping the shift count in a global variable instead of as a literal, or computing the shift separately into a variable (a global or volatile local) and doing the |, +, etc, on the variable. |
Left shifts by 32 or more, as an operand of +, -, &, |, or ^, (eg, ((X<<56) | (Y<<48))) may produce incorrect results. |
| CODEGEN-4622 |
Builtin test __has_builtin incorrectly claims to support many __builtin functions |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.2.LTS |
Do not use __has_builtin until it is fixed. |
MCU release 18.1.x.LTS added the __has_builtin feature to detect whether or not a particular builtin function was supported. However, this feature test mistakenly returned true for a great number of builtins that the TI compiler does not support. |
| CODEGEN-4605 |
Incompatible redeclaration error with -o4 when using anonymous unions |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.2.LTS |
Do not use anonymous structs or unions; give all struct members a name, even if it is never used. |
Anonymous structs and unions are a GCC extension. They are members of a parent structure and have no names. You access the elements inside them as if they were direct members of the parent class. If you have an anonymous struct or union inside a union and you use -O4 optimization, you may get the mistaken error "symbol so-and-so redeclared with incompatible type" at link time. This bug can only happen in COFF mode.
Essentially the same bug was previously fixed for EABI and was known as CODEGEN-1191. |
| CODEGEN-4600 |
Warning when using pragma RETAIN with attribute((noinit)) |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.3.LTS |
|
When using pragma RETAIN with attribute((noinit)) on the same symbol for an EABI target, a .clink directive is erroneously emitted in the assembly file, leading to a warning that the .CLINK directive is being ignored because the symbol already has .RETAIN specified. |
| CODEGEN-4581 |
Using the C interlister with C++14 features may generate error |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.2.LTS |
Do not use the -s source interlisting option |
When using the -s C source interlisting option, the compiler may emit a bogus assembly directive for functions which do not have a body in the source code (e.g. certain implicit constructors). The assembler will emit an error when encountering this directive. |
| CODEGEN-4576 |
hex --ascii option truncates address to 16 bits |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.2.LTS |
Use the hex converter from an earlier release |
When generating an "ASCII" format hex file, the hex converter would mistakenly truncate addresses to the lower 16 bits. |
| CODEGEN-4419 |
Compiler erroneously speculates indexed load from the stack |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.2.LTS |
Modify the source code of the offending function to make local variables "volatile." There's no obvious way to pre-determine that a function will suffer from this bug; you just have to wait for the bug to happen, look at the line number of the offending instruction (which will always be a load with indexed addressing with base register SP), and go to the function at that line number. Make every local variable in that function "volatile." If it's a C++ function, you may need to make the function "volatile." |
The compiler moves instructions from one block to another to increase parallelism. Usually this is done by predicating (adding a condition to) every instruction that is moved above a branch. However, in some cases, the compiler will "speculate" the instruction, which means removing the condition entirely. This is done when the instruction's side-effects are judged to be safe, such as load of a local variable. In the case that the instruction's condition would have been false, this load will be useless, but at least it will be safe, because the stack pointer (SP) is at a legal location, and there won't be a memory fault. However, when a local variable's value is read with an indexed expression, the index register is not necessarily speculated exactly when the load is, so the index register may have a garbage value. In this test case, the load was speculated, but the index register definition wasn't, so in the false branch, the computed address was garbage, and we would read a random memory address, causing a memory fault. (Even though SP was perfectly valid, the index register was garbage, so SP+index might point anywhere in memory.) |
| CODEGEN-4407 |
Not using const causes unexpected build error when calling std::sort |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.2.LTS |
Remove unnecessary const from helper in s__algo.c |
|
| CODEGEN-4339 |
div() and ldiv() return incorrect result when built with -o4 option |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.0.LTS |
|
|
| CODEGEN-4280 |
Using ULP advisor with C++ templates may cause the compiler to crash |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.2.LTS |
|
The compiler may crash when using ULP advisor on C++ code that contains templates |
| CODEGEN-4182 |
Should ignore option --pending_instantiations when compiling C files |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.2.LTS |
If the user wishes to use the option --pending_instantiations, they must add this option individually to each C++ file. |
The compiler option --pending_instantiations only makes any sense when used with C++ code. It cannot have any effect on C code. Indeed, when passed as an option to a compilation of C code, the compiler will stop and emit an error, "pending instantiations option can be used only when compiling C++"
This is troublesome when trying to compile a mixture of C and C++ files in CCS. If the user wishes to use the option --pending_instantiations, they cannot just add this option to the global compiler options list; they must add this option individually to each C++ file. |
| CODEGEN-4113 |
Assembler computes wrong result for expression 0x232800 % 0x10000 |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.2.LTS |
In some instances, as in the original test case, the AND operator can be used instead, but that is not a general workaround. |
The modulo operator in the TI assembler, for releases made in mid-to-late 2016 and all of 2017, is unreliable. In some cases it will produce an incorrect answer. |
| CODEGEN-4078 |
Linker takes over 5 minutes to finish |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.2.LTS |
None. If the linker command file wants to be that specific about memory ranges, then the work has to be done, and the option to disable the work has its own bug. |
Linking may take excessively long when the linker command file specifically places a lot of variables at specific addresses, especially for C2000. The original report was placing more than 300 variables. The --no_placement_optimization option is not a workaround because it causes a linker crash. Both problems are fixed together. |
| CODEGEN-3955 |
libc++ has incorrect implementation of pointer_safety |
Fixed |
|
MSP430_18.1.0.LTS |
|
The implementation of std::pointer_safety is a struct, rather than as an enum_class, as required by the C++ standard. |
| CODEGEN-3931 |
Compiler crashes while handling 0 length array in zero sized struct |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.2.LTS |
None |
The compiler crashes while parsing a struct or class with zero-sized members in C++ mode. |
| CODEGEN-3923 |
DWARF CFI information lost due to microoptimizations |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.3.LTS |
No practical workaround. |
Some optimizations in the compiler would change instructions but fail to retain debugging directives attached to those instructions. This could impact the accuracy of the DWARF debugging information in various ways. |
| CODEGEN-3918 |
Writing multiple input sections in one line unexpectedly changes how input sections are combined into output sections |
Fixed |
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_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_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-3794 |
False warning for MISRA 10.1/10.2 when commutative binary operands swapped |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.2.LTS |
|
In certain cases, the compiler could emit an unwarranted MISRA diagnostic about type conversion. This would occur when using a commutative binary arithmetic operator with mixed operand types. The compiler mistakenly compared one operand's type to the other type. It should have compared each type to the promoted type of the operation. |
| CODEGEN-3619 |
pragma triggers false MISRA-C:2004 19.1/A warning |
Fixed |
|
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-3595 |
Stack usage under reports stack amount used because it fails to handle function aliases |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.2.LTS |
|
CCS Stack Assistant did not accurately track aliased functions-- functions whose definitions are represented by a different symbol name. Now, the alias function will be used to determine stack size correctly, and the aliased function call name will be replaced with its alias. Currently, the Stack Assistant GUI is not capable of showing both the aliased and alias function names for calls to aliased functions-- this will require a future update. |
| CODEGEN-2373 |
Internal linker error triggered by function alias |
Fixed |
|
MSP430_18.1.0.LTS |
|
Linker sometimes generates "Assertion failed" message and aborts. |
| CODEGEN-1979 |
Statements before declarations with no white space (aggravated by macros) may cause incorrect parser error |
Fixed |
|
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. |
| SDSCM00050131 |
Local struct with non-constant initializer treated as static scope variable |
Fixed |
MSP430_18.1.0.LTS |
MSP430_18.1.5.LTS |
Completely specify every aggregate member in the initializer, or do not provide an initializer at all and instead populate each field with a statement. |
Function local non-static aggregate (array or struct) variables which are initialized to zero, or with an initializer that incompletely specifies all of the aggregate members, will be converted to static scope (global) objects. This is wrong; each time the function is entered, there should be a fresh copy of the variable. |
