blob: 814f8991f9eebc218251b906bc159cdc381a25b8 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, so I'm trying to figure out what category this bug falls into for QEMU. The problem is about an instruction not being emulated correctly—the ADDV opcode.
Looking at the description, the user says that according to the documentation, ADDV Rm, Rn should add Rm and Rn, store the result in Rn, and set the overflow flag T. But in QEMU, it's storing the result in Rm instead of Rn. That means the instruction is being handled incorrectly.
The steps to reproduce involve a C program that uses inline assembly with ADDV. The real hardware gives different results than QEMU when this instruction is used. So, the issue isn't with a system call or something happening during runtime; it's specifically about how an instruction is emulated in QEMU.
So, I think the category should be 'instruction' because it's directly related to how a specific CPU instruction is handled.
</think>
The bug report describes an issue where the ADDV instruction is not being emulated correctly by QEMU. The problem lies in the handling of this specific instruction, which falls under the 'instruction' category.
instruction
|