On 25/7/25 08:17, Paolo Bonzini wrote:
Table A-5 of the Intel manual incorrectly lists the third operand of
VINSERTx128 as Wqq, but it is actually a 128-bit value. This is
visible when W is a memory operand close to the end of the page.
Fixes the recently-added poly1305_kunit test in linux-next.
(No testcase yet, but I plan to modify test-avx2 to use memory
close to the end of the page. This would work because the test
vectors correctly have the memory operand as xmm2/m128).
Fixes: 79068477686 ("target/i386: reimplement 0x0f 0x3a, add AVX")
Reported-by: Eric Biggers <ebigg...@kernel.org>
Cc: Ard Biesheuvel <a...@kernel.org>
Cc: "Jason A. Donenfeld" <ja...@zx2c4.com>
Cc: Guenter Roeck <li...@roeck-us.net>
Signed-off-by: Paolo Bonzini <pbonz...@redhat.com>
---
target/i386/tcg/decode-new.c.inc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
