blob: 6bb287711b3cae33be42a4a50b2a63f5bf1e4cbf (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, so I'm trying to figure out whether this bug report is about user-mode or system-mode in QEMU. Let's break down the information provided.
The user mentions they're running GCC tests on a target using QEMU with the arm926 CPU and the --cpu arm926 option. They configured GCC to generate arm10tdmi code by default, including VFP support. The issue is that after updating QEMU to master, they noticed regressions in their tests compared to QEMU 3.1.
I know that user-mode emulation typically runs applications without a full OS, handling just the CPU and basic syscalls. System-mode, on the other hand, emulates a full system, including devices, peripherals, and higher-privilege operations.
In this case, the user is running GCC tests which are likely application-level binaries. They're using QEMU with specific CPU settings but haven't mentioned any device emulation or OS-specific issues beyond what's needed for the test setup. The script they provided probably runs these tests in a simple environment without needing to boot an entire OS.
So, since the issue is about running user-space applications (GCC tests) and not involving system-level components like devices or full OS behavior, this seems related to user-mode emulation.
</think>
user
|