This is a list of currently open issues for the TASKING VX-toolset for Power Architecture v2.1r1.
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.1r1 is included in the release notes of the product.
ID | Summary |
| POWERVX-165 |
Linker warning when using __at() on __sdata0 objects |
| POWERVX-278 |
ccppc does not use backslash in library paths for win32 |
| POWERVX-310 |
e200z0 needs an alternative interrupt vector solution |
| POWERVX-398 |
__get_return_address() doesn't work in combination with call-return optimization |
| POWERVX-541 |
Improve VLE instruction support in assembler |
| POWERVX-573 |
HLL symbol table: hide pointer qualifiers in argument lists |
| POWERVX-583 |
e200z0 support must be added to the exception handling in the simulator |
| POWERVX-594 |
Disassembly gives question marks for section .test_vle.printf.libc |
| POWERVX-599 |
Simulator exception handling erroneously clears flags |
| POWERVX-601 |
MIL linking results in type check errors because of thresholds |
| POWERVX-604 |
In debugger, windows are not updated, after stepping through the program |
| POWERVX-607 |
Make enums compliant to 2011 EABI |
| POWERVX-609 |
The ABI requires long-long bitfields to be implemented |
| POWERVX-611 |
ABI requires 16-byte alignment of the stack-pointer. |
| POWERVX-661 |
preprocessor ignores definitions in nested includes |
| POWERVX-668 |
@CPU assembly function doesn't work. |
| POWERVX-683 |
Different behavior of Cyclone MAX, Multilink and Multilink FX |
| POWERVX-686 |
EABI requires different prototype of __va_start() intrinsic |
| POWERVX-698 |
Incorrect order of parameters of .PAGE control in the manual |
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.1r1 is not shown here, it is included in the release notes of the product.