This is a list of currently open issues for the TASKING VX-toolset for RISC-V v1.1r2. The list may include issues found in later releases, whether such issues also appear in this releasehas not always been verified yet. See below for the list of closed issues. The list of fixed issues for v1.1r2 is included in the release notes of the product.
| ID | Summary |
| RISCV-100 | Storing the address of a static local variable in another can lead to incorrect optimizations |
| RISCV-101 | If a function call has sibling expressions, loads can be incorrectly reordered |
| RISCV-103 | C compiler error S900 internal consistency check failed |
| RISCV-104 | Storing 24-bit structures may overwrite 32 bits of memory |
| RISCV-105 | Signed long long multiplications can be miscompiled |
| RISCV-106 | Option --tune=arcv-rhx100 produces incorrect code |
| RISCV-115 | Incorrect translation of code with loops |
| RISCV-116 | Linker may report an error on unused undefined (extern) locator symbols for a stack |
| RISCV-119 | Function call relaxation may break code alignment |
| RISCV-120 | Compiler generates incorrect code for crc function |
| RISCV-128 | Preprocessor output is not included in the given output folder |
| RISCV-131 | Erroneous code generated for a use case including a ternary expression |
| RISCV-135 | Struct fields may get overwritten when assigning to fields in nested structs |
| RISCV-19 | Wrong result after comparison |
| RISCV-80 | Assembler inserts zeros instead of NOPs when using .ALIGN directive in code sections |
| RISCV-85 | LSL group priority is not applied to sections with a range restriction |
| RISCV-86 | LSL range restriction with different LSL group priorities is not split up on priority |
| RISCV-92 | Interrupt handlers do not always save and restore x5 when they should |
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 v1.1r2 is not shown here, it is included in the release notes of the product.