blob: c112f41c61c42d529e569ce33b55510e655203d1 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
|
<think>
Alright, I need to classify this bug report for QEMU into one of three categories: instruction, syscall, or runtime. Let's break down the information provided.
The user is reporting regressions when running GCC tests on the arm-linux-gnueabihf target using a recent version of QEMU (master branch). They mention that all tests used to pass but now cause QEMU to crash after applying a specific fix. The tests involve binaries, shared libraries, and a script.
The possible categories are:
1. **Instruction**: This would be if the issue is related to how certain CPU instructions are handled.
2. **Syscall**: If the problem involves system calls not working as expected.
3. **Runtime**: Any other runtime issues that don't fall into the above two categories.
Given the context, the user isn't pointing out a specific instruction or syscall failure but rather general crashes when running tests. This suggests it's a broader runtime issue affecting how QEMU handles these test cases after the fix. Therefore, the category is likely **runtime**.
</think>
The bug report involves general runtime issues causing QEMU to crash during GCC tests, not specifically tied to instructions or syscalls.
runtime
|