This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hello,
We are developing a medical device, and as part of this process, we need to catalog all open bugs related to the compiler we are using (TI compiler).
As of today, there are some bugs that were reported a few years ago which remain unresolved.
I am unsure if these bugs are relevant to our project: there are two bugs that I do not fully understand:
CODEGEN-1476:
EXT_EP-8121:
https://sir.ext.ti.com/jira/browse/EXT_EP-8121
"Incorrect value assigned to a forward reference of a symbol defined in terms of the section's PC ($) after jump expansion"
This bug is related to assembly (asm) code, and the suggested workaround also involves asm code.
In our product, we do not utilize assembler code, but we need to ascertain whether the compiler recognizes this issue and if there is a possibility of encountering such a problem in our context.
I was unable to find any 'space directive' in the assembler code generated by dis430. The process I followed was:
> /opt/ti/ccs1120/ccs/tools//compiler/ti-cgt-msp430_21.6.0.LTS/bin/dis430 Release/ICU_FW.out > icu_rel.asm
> grep -ri space icu_rel.asm => return nothing.
Based on this, can I be confident that the 'space directive' is not used in our project?
CODEGEN-322:
EXT_EP-8023
https://sir.ext.ti.com/jira/browse/EXT_EP-8023
"Structure is not initialized correctly when using -o2 or -o3 optimization"
Is this bug still unresolved? Does this bug occur only when initializing a structure using symbols generated by the linker's CMD file?
CODEGEN-1476:
EXT_EP-8121:
For more context, here is the forum thread which resulted in this entry being filed. It can only occur in hand-coded assembly. Since ...
we do not utilize assembler code
... you can ignore it.
CODEGEN-322:
EXT_EP-8023
And here is the forum thread which resulted in this entry being filed. Again, you can ignore it. This happened long ago, before EABI was supported. The circumstances of this bug can only occur in the older COFF ABI, and not the newer EABI.
Thanks and regards,
-George
**Attention** This is a public forum