This is a list of currently open issues for the TASKING VX-toolset for RISC-V v1.0r1. 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.0r1 is included in the release notes of the product.
| ID | Summary |
| RISCV-11 | Group placement constraint ignored when a generic section selection is used using wildcard pattern '*' |
| RISCV-19 | Wrong result after comparison |
| RISCV-26 | MRET/SRET instruction is replaced with CM.POPRET |
| RISCV-28 | Some library routines are incompatible with trampolines |
| RISCV-36 | Erroneous struct size using __packed__ attribute in a type definition which uses bitfields |
| RISCV-37 | C Compiler: Wrong constant propagation when aliasing |
| RISCV-39 | Linker does not always generate trampoline when it should |
| RISCV-46 | Incorrect store_load optimization when the stack frame is large |
| RISCV-50 | CM.MVA01S and CM.MVSA01 instructions cannot be used with option --rve |
| RISCV-51 | Undetected aliases generated by function calls on local pointers |
| RISCV-53 | Incorrect aliasing analysis of restrict pointer expression after PRE while strength reduction is disabled |
| RISCV-64 | Pointsto analysis can get confused by aliases |
| RISCV-67 | Run-time comparison to a floating-point NaN returns true in some cases |
| RISCV-69 | Variable-length arrays are always word-aligned |
| RISCV-74 | Identical calls or other side effects can be dropped in a range test |
| RISCV-79 | Alias analysis can fail when stores are merged and MIL linking is used |
| 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-93 | Code compaction may break interrupt handlers |
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.0r1 is not shown here, it is included in the release notes of the product.