blob: 1bd595c4a213901a632ff19547d7d5895ce87704 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Okay, I need to classify this bug report as either user-mode or system-mode related. The issue is about GDB debugging in QEMU where V registers can't be accessed unless single-letter V is enabled. Hmm.
I remember that GDB interacts with the target's registers. V registers are vector registers, often used in SIMD operations. If accessing them requires a specific flag, it might relate to how the CPU handles these registers in user space.
User-mode typically deals with application-level issues without needing high privileges. Since this is about debugging and register access, which GDB does as part of normal user-space debugging, it's likely user-mode.
System-mode would involve lower-level stuff like device drivers or OS internals, but this seems more about the CPU's state accessible to the debugger. So probably not system-mode.
Therefore, I'll classify this as a 'user' mode issue.
</think>
The bug report is related to accessing V registers during GDB debugging in QEMU. This involves user-space debugging and register access without requiring higher privileges or interacting with system-level components like peripherals or the OS kernel.
user
|