blob: 3ed1056620bae3758874fc409fca911945de9710 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
|
<think>
Alright, I'm trying to figure out how to classify this bug report as either 'instruction', 'syscall', or 'runtime'. Let's break down what the user provided.
The problem occurs when running code using QEMU on a LoongArch host. The issue is with LSX vector instructions getting wrong results. They built Linux-user for LoongArch, ran some tests, and observed incorrect outputs compared to when they run the same code natively or under QEMU on x86_64.
First, I think about what each category entails:
1. **Instruction**: This would involve a bug where specific instructions are mishandled by QEMU. Since LSX is mentioned specifically, it's possible that QEMU isn't emulating these vector instructions correctly.
2. **Syscall**: This relates to errors in system calls. The problem here doesn't mention any issues with system calls but rather incorrect results from computations.
3. **Runtime**: This covers other runtime errors not falling into the above categories. However, since the issue is specifically about instruction handling, it's more likely related to instructions than a general runtime error.
Given that the problem arises during vector operations using LSX instructions and the output differs when run under QEMU versus native or another architecture, this points towards an issue with how QEMU handles these specific instructions. Therefore, it's most likely an 'instruction' category bug.
</think>
The bug is related to incorrect handling of specific vector instructions (LSX) in QEMU, which falls under instruction-level issues.
instruction
|