FEX/unittests/ASM/VEX/vpmaxsb.asm
Lioncache 65eec673fc VectorOps: Handle more VSMax SVE cases better
Since SMAX performs a comparison and returns the max value regardless
of how the operands are provided, we can check for when the second
input aliases the destination.
2023-10-18 18:48:03 +02:00

52 lines
1.5 KiB
NASM

%ifdef CONFIG
{
"HostFeatures": ["AVX"],
"RegData": {
"XMM0": ["0x4142434445464748", "0x7172737475767778", "0x4142434445464748", "0x7172737475767778"],
"XMM1": ["0x8062636465666768", "0x5152535455565758", "0x6162636465666768", "0x5152535455565758"],
"XMM2": ["0x4162636465666768", "0x7172737475767778", "0x0000000000000000", "0x0000000000000000"],
"XMM3": ["0x4162636465666768", "0x7172737475767778", "0x6162636465666768", "0x7172737475767778"],
"XMM4": ["0x4162636465666768", "0x7172737475767778", "0x0000000000000000", "0x0000000000000000"],
"XMM5": ["0x4162636465666768", "0x7172737475767778", "0x6162636465666768", "0x7172737475767778"],
"XMM6": ["0x4162636465666768", "0x7172737475767778", "0x6162636465666768", "0x7172737475767778"],
"XMM7": ["0x4162636465666768", "0x7172737475767778", "0x6162636465666768", "0x7172737475767778"]
},
"MemoryRegions": {
"0x100000000": "4096"
}
}
%endif
lea rdx, [rel .data]
vmovapd ymm0, [rdx]
vmovapd ymm1, [rdx + 32]
vpmaxsb xmm2, xmm0, xmm1
vpmaxsb ymm3, ymm0, ymm1
vpmaxsb xmm4, xmm0, [rdx + 32]
vpmaxsb ymm5, ymm0, [rdx + 32]
; Some funky combinations for testing fast paths
; Related to SVE sources aliasing the destination
vmovapd ymm6, ymm0
vpmaxsb ymm6, ymm6, ymm5
vmovapd ymm7, ymm0
vpmaxsb ymm7, ymm5, ymm7
hlt
align 32
.data:
dq 0x4142434445464748
dq 0x7172737475767778
dq 0x4142434445464748
dq 0x7172737475767778
dq 0x8062636465666768
dq 0x5152535455565758
dq 0x6162636465666768
dq 0x5152535455565758