blob: 09941d93abadbc0331dc81505b0051988b8d3673 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
|
<think>
Okay, so I'm looking at this bug report from a user about QEMU. They want to add support for more ARM CPUs in their environment. Let me break down what's going on here.
First, the user mentions they're using QEMU for GCC validations. That makes sense because GCC is a compiler, and you'd want to test that it generates correct code for different CPU architectures. The user lists several Cortex-M and Cortex-A series processors they want support for. These are ARM cores used in various embedded systems and mobile devices.
They ask if it's possible to add these CPUs, where to report this, and whether separate requests are needed. Now, the task is to classify this bug report as either 'user-mode' or 'system-mode'.
From what I know, QEMU has two main modes: user mode and system mode. User mode allows running individual applications without a full OS, which is great for testing binaries against different architectures. System mode simulates an entire system with hardware devices, peripherals, etc., and is used more for virtualization.
The user specifies that they're interested in user-mode support. They’re likely concerned with the CPU instruction set and ensuring GCC doesn't generate unsupported instructions. So this would fall under user-mode since it's about running binaries on different CPUs without needing full system emulation.
I don’t think they need separate bug reports for each CPU because the request is about adding multiple similar architectures. But maybe that’s up to the QEMU maintainers. However, the classification here should be 'user' mode.
</think>
The user is requesting support for additional ARM CPUs in QEMU specifically for GCC validation in user-mode. This relates to running applications and testing instruction sets rather than emulating a full system.
Answer: user
|