blob: cff144aeedcac2d0665a25d676846a3db16e8e25 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
|
<think>
Okay, I need to classify this bug report as either 'user-mode' or 'system-mode'. Let's break it down.
The issue is about incorrect behavior of SDOT and UDOT instructions in QEMU when using the sve-default-vector-length >=64. The user provided a C program that uses SVE intrinsics and observed discrepancies between expected and actual results in QEMU simulations, especially with higher vector lengths.
From the steps to reproduce, it looks like the problem occurs during user-space execution. They compile a test program, run it under QEMU, and observe incorrect output. The assembly instructions generated (sdot) are correct according to ACLE, so the issue isn't in the compiler but likely in how QEMU handles these instructions.
System-mode issues typically involve higher privileges like kernel operations, device drivers, or hardware emulation at a deeper level. This bug seems to be about user-space code execution and how QEMU's SVE implementation is handling specific vector operations. Since it's about executing user-level instructions incorrectly, it falls under user-mode.
</think>
user
|