blob: 2739dbbd357d7b0a3615c67451a3ec583a7bb462 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, I need to classify this bug report as either 'user-mode' or 'system-mode'. Let me read through the problem description carefully.
The issue is about a QEMU assertion failure when executing RISC-V RVV instructions. The specific instruction causing the problem is vmv.v.x with e64 and vl == vl_max on an RV32 guest. The error occurs in tcg_gen_gvec_dup_i32 because vece is MO_64, which exceeds MO_32.
Looking at the steps to reproduce, it involves setting up a vector environment using vsetvli and then executing vmv.v.x. This seems like user-level code execution since these are standard RISC-V instructions used in application-level programming. There's no mention of higher-privilege operations or interaction with peripherals or devices.
The provided solution suggests modifying how the gvec_dup is generated, specifically handling 64-bit elements correctly when running on a 32-bit target. This fix is within the translation layer of QEMU for user-mode emulation.
Since the problem arises from executing user-level vector instructions and doesn't involve system-level components like device drivers or OS interactions, it's likely related to user-mode operations.
</think>
user
|