blob: d32449d8347c147a7774a4b6ad5e6a34351f90ba (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
|
<think>
Okay, I need to classify this bug report into one of the given categories: instruction, syscall, or runtime. Let's read through the problem description carefully.
The issue is about QEMU 3.1 incorrectly decoding a 'c.unimp' instruction as 'addi4spn fp, 0'. The problem arises because when handling compressed instructions, only the lower 16 bits are valid, but the current code uses a 32-bit load for ctx->opcode, which includes more bytes than it should. This causes reserved or illegal opcodes to be misdecoded.
This sounds like an issue with how the emulator decodes and handles specific machine instructions. It's not related to system calls (syscall) because it doesn't involve interacting with the OS kernel. It also doesn't seem like a runtime error in general, as it's specifically about instruction decoding. Instead, it falls under incorrect handling of an instruction.
So, the category should be 'instruction'.
</think>
instruction
|