1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
|
<think>
Okay, I'm trying to classify this bug report for QEMU. The user provided a detailed bug where compiling libpaper using GCC in qemu-user sparc64 leads to a segfault and an internal compilation error. Let's break down the information.
First, the issue occurs during building with QEMU User mode on Sparc64. When trying to compile libpaper, it fails with a GCC ICE (Internal Compiler Error). The user also mentions that using `gcc -mcpu=ultrasparc -O2 -c` directly causes the same error, and provided an output file.
Looking at the categories given: mistranslation, assembly lowering, device, graphic, socket, network, KVM, boot, vnc, debug, files, permissions, performance, kernel, peripherals, hypervisor, other.
Since this is happening during GCC's compilation process in QEMU User mode (which translates Sparc64 code to something the host can run), it's likely related to how QEMU handles the translation. The error happens at the assembly level or during the lowering phase from the source architecture (Sparc64) to the target.
The key here is that it's an internal compiler error triggered by GCC when using QEMU. This suggests a problem in how QEMU translates Sparc64 instructions, which affects the GCC compilation process. Therefore, this falls under 'assembly lowering' because it's about translating machine code instructions.
I don't see any mention of devices, graphics, networking, etc., so other categories like device or network aren't relevant here. It's more about the translation layer rather than performance issues or kernel problems. So, the most appropriate category is 'assembly'.
</think>
The bug occurs during GCC's compilation process within QEMU User mode on Sparc64. The error arises due to an internal compiler issue when using specific flags, pointing to a problem in how QEMU translates instructions from Sparc64 to the host architecture. This relates directly to assembly lowering.
**Answer:** assembly
|