This is a list of currently open issues for the TASKING VX-toolset for MCS v2.0r1.
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 v2.0r1 is included in the release notes of the product.
ID | Summary | Inspector detector |
| MCSVX-136 |
asmcs E208: syntax error: "TBU_TS0" unexpected despite note in TC29x A manual |
Not planned |
| MCSVX-206 |
Incorrect stack offsets in debug info |
Not planned |
| MCSVX-266 |
Assembler does not correctly set the MCS core flag in the object file |
Not planned |
| MCSVX-311 |
Perennial-c tests P50033.c causes register allocation faillure for function "test_for" |
Not planned |
| MCSVX-314 |
Perennial-c tests fails on constant folding of offsetof() macro |
Not planned |
| MCSVX-326 |
Incorrect address calculation for MRDI instruction |
Not planned |
| MCSVX-415 |
Update cnvba2ta.pl script |
Not planned |
| MCSVX-476 |
The instructions addl, subl, etc. give a "cannot emit expression" error |
Not planned |
| MCSVX-517 |
Linker gives "internal error" when adding/subtracting labels in assembly source |
Not planned |
| MCSVX-623 |
Erroneous result with peephole optimization |
Not planned |
| MCSVX-639 |
The GTM toolset should support up tot 10 MCS cores |
Not planned |
| MCSVX-641 |
Wide character support shall not be used in safety critical applications |
Not planned |
| MCSVX-733 |
Incorrect merging of consecutive updates of the same array member |
Not planned |
| MCSVX-735 |
C compiler cmcs: global volatile variable ignored in loop |
Not planned |
| MCSVX-736 |
C compiler cmcs: incorrect array operation |
Not planned |
| MCSVX-737 |
Expression reshuffling may lead to out-of-bounds address |
Not planned |
| MCSVX-758 |
Setting a breakpoint in a channel other than channel_0 does not work |
Not planned |
| MCSVX-760 |
Channel local stacks are not listed in the map file |
Not planned |
| MCSVX-764 |
C compiler cmcs S917: internal consistency check failed error due to __aei pointer constant plus variable index addressing |
Not planned |
| MCSVX-774 |
Control program always creates an ELF output file |
Not planned |
| MCSVX-788 |
C compiler error cmcs S917: internal consistency check failed - please report |
Not planned |
| MCSVX-801 |
Perennial C P64072 fails on overlapping struct initialization |
Not planned |
| MCSVX-806 |
MCS assembler emits wrong code when --extended-registers option is not set |
Not planned |
| MCSVX-809 |
Wrong address specification for FIFO register |
Not planned |
| MCSVX-884 |
MSB (bits 31-24) not cleared in memory after storing a 24-bit value |
Not planned |
| MCSVX-918 |
Optimization ignores __weak__ attribute in the code |
Not planned |
| MCSVX-920 |
Missing diagnostic message W507 variable is possibly uninitialized |
Not planned |
| MCSVX-939 |
C compiler may leave empty .src file when it is killed |
Not planned |
| MCSVX-940 |
Compiler generates wrong code for loops with 64-bit iterators |
Not planned |
| MCSVX-946 |
C Compiler: _Bool - incorrect expression evaluation |
Not planned |
| MCSVX-970 |
Common debug info section generated by C compiler may contain references to code sections |
Not planned |
| ID | Summary |
| MCSVX-182 |
Full Special Function Register (SFR) support in C compiler |
| MCSVX-321 |
Intrinsic functions prototypes v3.1r1 are depricated and will change in the next release |
| MCSVX-322 |
Directives .COMPILER_NAME, .COMPILER_VERSION & .COMPILER_INVOCATION are not supported |
| MCSVX-330 |
The MCS assembler accepts register addresses |
| MCSVX-484 |
Hldump supports BOSCH Address List Format for A2L Address Calculation |
| MCSVX-545 |
Support the new C-array output format |
| MCSVX-647 |
Provide compete set of Special Function Register (SFR) files |
| MCSVX-648 |
Optimization improvements and EABI changes |
| MCSVX-649 |
The set of intrinsic functions and associated data types has changed. |
| MCSVX-650 |
Optional software implementation for multiply and divide operations |
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 v2.0r1 is not shown here, it is included in the release notes of the product.