Open and Closed Issues for TASKING VX-toolset for MCS v3.2r1Log in

Open Issues

This is a list of currently open issues for the TASKING VX-toolset for MCS v3.2r1. 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.2r1 is included in the release notes of the product.


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-641 Wide character support shall not be used in safety critical applications
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-774 Control program always creates an ELF output file
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
MCSVX-888 Function fesetexceptflag() may incorrectly raise FE_INEXACT
MCSVX-896 C library function strtof might incorrectly return INIFINITY for hexadecimal number

Closed Issues

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.2r1 is not shown here, it is included in the release notes of the product.

Not a problem

MCSVX-680 Intrinsic for WURM instruction missing

Table of ContentsBack