Open and Closed Issues for TASKING VX-toolset for RISC-V v1.2r1HomeLogin

Open Issues

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

Problems

IDSummary
RISCV-104 Storing 24-bit structures may overwrite 32 bits of memory
RISCV-142 Compiler produces incorrect code for a vararg function when parameter is a struct
RISCV-155 C compiler criscv ignores __attribute__(( section("...") )) and __section__("...")
RISCV-167 Incorrect code generated for 64-bit multiply by constant when using --tune=arcv-rhx100
RISCV-169 Calls to a weak-aliased symbol are resolved directly instead of at link-time
RISCV-170 C compiler mis-evaluates inline chained relational/bitwise comparison on unsigned char, computing wrong boolean result
RISCV-171 Potentially wrong results from R_RISCV_PCREL_LO12_I and R_RISCV_PCREL_LO12_S relocation functions
RISCV-176 Incorrect handling of large struct variadic arguments
RISCV-180 Using linker symbols may lead to duplicate global symbols with different values
RISCV-183 CRC recognition is not precise enough
RISCV-184 Widening conversion after addition with constant might lose wraparound behavior
RISCV-185 Option -Av is not always honored
RISCV-186 Linker does not update DWARF values when relaxation is enabled
RISCV-187 Linker can remove a lui for higher bits that was still used during relaxation optimization
RISCV-192 Function merging optimization redirects calls to weak functions
RISCV-194 Statement expressions can crash the compiler or produce wrong code
RISCV-195 GCC statement-expression ({ ... }) silently drops instructions in some cases
RISCV-197 Early return and conditional call at function end may corrupt caller's stack
RISCV-206 Sequenced stores to a volatile object are combined into a single unconditional write
RISCV-209 Interrupt handlers do not save and restore vector registers
RISCV-210 std::exception_ptr comparison and rethrow_exception give incorrect results
RISCV-211 Compression of prologues and epilogues with run-time library routines breaks interrupt handlers
RISCV-216 Miscompilation for always-false range checks
RISCV-218 Floating-point literal parser mis-rounds an exact round-to-nearest-even tie
RISCV-233 Generic assembly code optimization causes read from uninitialized address
RISCV-234 Register x5 can be clobbered by interrupt handlers
RISCV-238 Relaxation interferes with computing addresses of objects in sections with absolute addresses
RISCV-245 Global state is not preserved during interrupt handler execution
RISCV-246 Compiling with Zcmp extension can lead to stack corruption
RISCV-251 Vector register saves with --rvv-vector-bits >= 128 in prolog/epilog can lead to stack corruption
RISCV-257 GLO optimization in combination with __interrupt qualifier or interprocedural register optimization may lead to clobbered caller-saved registers
RISCV-261 Large aggregates are passed incorrectly
RISCV-266 Option --tune=arcv-rhx100 produces incorrect code
RISCV-267 Epilogue may free stack frame too soon
RISCV-268 Option --tune=arcv-rhx100 might ignore volatile access order
RISCV-276 Invalid code when accessing nested CSRs
RISCV-279 Some predefined macros are incorrect

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

Table of Contents