blob: 153973e61221ef63935d6f033a5c25953193a302 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, let's see. The user provided a bug report about Qemu's handling of the LoongArch64 `xvldi` instruction. The problem is that when they run a C++ program using this instruction, the output differs between real hardware and Qemu. The expected output is all 0x00000800 values, but Qemu produces alternating 0x08000800 and zeros.
Looking at the code, the issue is in the `vldi_get_value` function within Qemu's source. The case for 1 is supposed to generate a 32-bit pattern. The current code does `(t << 24) | (t << 8)`, but the user suggests it should be `(t << (8+32)) | t << 8`. Wait, shifting by 32 bits in a 32-bit integer would zero it out. Maybe the data is being treated as 64-bit? Or perhaps the LoongArch instruction expects the immediate to be replicated in a certain way across the vector.
The `xvldi` instruction is a vector load immediate. The description mentions replicating a byte shifted left by 8, resulting in 0x800 (which is 0x0800 in hex). On real hardware, each 32-bit word is 0x00000800. But Qemu's code is creating a pattern where the immediate is placed at both high and low positions in a 64-bit context, leading to 0x08000800 when stored as a 32-bit value.
The user points out that the Qemu code for case 1 is using `(t << 24) | (t << 8)`, which would create a 32-bit value with the immediate in bits 8-15 and 24-31. But when this is stored into a 32-bit word, it would result in 0x08000800. However, the correct value should be 0x00000800 repeated. So the problem is that Qemu's implementation of the `xvldi` instruction is incorrect. The suggested fix is to shift one part by 32+8 bits. Maybe the original code is handling 64-bit elements? Or perhaps the instruction's encoding requires replicating the immediate into specific positions across multiple 32-bit words.
Since the issue is in the translation of the `xvldi` instruction's immediate value into the correct vector pattern, this is a direct error in how the instruction is implemented in Qemu. Therefore, the category should be "instruction".
</think>
instruction
|