This is a list of currently open issues for the TASKING VX-toolset for MCS v3.1r2.
The list may include issues found in later releases, whether such issues also appear in this release has not always been verified yet. See below for the list of closed issues. The list of fixed issues for v3.1r2 is included in the release notes of the product.
ID | Summary |
MCSVX-136 |
asmcs E208: syntax error: "TBU_TS0" unexpected despite note in TC29x A manual |
MCSVX-517 |
Linker gives "internal error" when adding/subtracting labels in assembly source |
MCSVX-639 |
The GTM toolset should support up tot 10 MCS cores |
MCSVX-641 |
Wide character support shall not be used in safety critical applications |
MCSVX-733 |
Incorrect merging of consecutive updates of the same array member |
MCSVX-735 |
C compiler cmcs: global volatile variable ignored in loop |
MCSVX-736 |
C compiler cmcs: incorrect array operation |
MCSVX-737 |
Expression reshuffling may lead to out-of-bounds address |
MCSVX-758 |
Setting a breakpoint in a channel other than channel_0 does not work |
MCSVX-760 |
Channel local stacks are not listed in the map file |
MCSVX-764 |
C compiler cmcs S917: internal consistency check failed error due to __aei pointer constant plus variable index addressing |
MCSVX-774 |
Control program always creates an ELF output file |
MCSVX-788 |
C compiler error cmcs S917: internal consistency check failed - please report |
MCSVX-801 |
Perennial C P64072 fails on overlapping struct initialization |
MCSVX-806 |
MCS assembler emits wrong code when --extended-registers option is not set |
MCSVX-809 |
Wrong address specification for FIFO register |
MCSVX-873 |
Incorrect number of loop iterations |
MCSVX-882 |
Compiler does not use extended register set in obvious use case |
MCSVX-884 |
MSB (bits 31-24) not cleared in memory after storing a 24-bit value |
MCSVX-887 |
Superfluous stack usage in a use case not using -t4 size optimization |
This is a list of issues that have been closed with a resolution other than fixed. This list contains issues that will not be fixed, issues that appeared to be not a problem and/or issues that could not be reproduced. The list of fixed issues for v3.1r2 is not shown here, it is included in the release notes of the product.