blob: 2edff4bf18cde2e26d3d5bdb655d6c93331f2d1b (
plain) (
blame)
1
2
3
4
5
6
7
|
<think>
Okay, let's see. The user is reporting a bug in QEMU related to the `vsetvli` instruction not setting the `vill` register when it should. According to the RISC-V Vector spec, when a reserved `vsetvli` instruction is used (like when changing VLMAX), implementations may set `vill`. The test case provided shows that QEMU doesn't set `vill` in such cases, leading to a failed assertion.
So, the problem is with the execution of the `vsetvli` instruction. The bug is specifically about how QEMU handles this instruction, not a syscall or runtime environment issue. The issue is in the instruction's implementation within QEMU. Therefore, the category should be "instruction".
</think>
instruction
|