Some RISC-V instructions perform writes to 2 destinations, either 2 register or register or program counter. In cases if the source of one sub-operation matches a destination of another one, the order of result output is important. The examples are jalr and instruction operating with CSRs:

riscv/riscv-tests#258
riscv/riscv-tests#263

Your obj

Set the thread name pthread_setname_np. This makes debugging easier. You know plugin is responsible for each thread without diving into it. When a segfault appears, you can assign blame by reading the threadname rather than inspecting the stacktrace.