podman
4628 строк · 260.3 Кб
1// Code generated by x86avxgen. DO NOT EDIT.2// VEX instructions that come in two forms:6// VTHING xmm2/m128, xmmV, xmm17// VTHING ymm2/m256, ymmV, ymm18//9// The opcode array in the corresponding Optab entry10// should contain the (VEX prefixes, opcode byte) pair11// for each of the two forms.12// For example, the entries for VPXOR are:13//14// VPXOR xmm2/m128, xmmV, xmm115// VEX.NDS.128.66.0F.WIG EF /r16//17// VPXOR ymm2/m256, ymmV, ymm118// VEX.NDS.256.66.0F.WIG EF /r19//20// Produce this optab entry:21//22// {AVPXOR, yvex_xy3, Pavx, opBytes{vex128|vex66|vex0F|vexWIG, 0xEF, vex256|vex66|vex0F|vexWIG, 0xEF}}23//24// VEX requires at least 2 bytes inside opBytes:25// - VEX prefixes (vex-prefixed constants)26// - Opcode byte27//28// EVEX instructions extend VEX form variety:29// VTHING zmm2/m512, zmmV, zmm1 -- implicit K0 (merging)30// VTHING zmm2/m512, zmmV, K, zmm1 -- explicit K mask (can't use K0)31//32// EVEX requires at least 3 bytes inside opBytes:33// - EVEX prefixes (evex-prefixed constants); similar to VEX34// - Displacement multiplier info (scale / broadcast scale)35// - Opcode byte; similar to VEX36//37// Both VEX and EVEX instructions may have opdigit (opcode extension) byte38// which follows the primary opcode byte.39// Because it can only have value of 0-7, it is written in octal notation.40//41// x86.csv can be very useful for figuring out proper [E]VEX parts.42}46}50}54}58}65}69}73}78}83}88}99}105}110}118}122}127}136}147}156}161}166}170}177}184}189}198}206}217}228}234}239}248}259}270}275}281}287}296}301}306}317}330}339}344}348}353}362}366}370}375}384}389}396}401}407}416}421}426}431}436}444}452}456}460}468}473}482}493}497}504}509}514}519}523}527}534}553}560}571}578}593}598}605}610}618}626}637}652}669}675}683}692}703}707}715}736}748}761}770}775}781}790}799}808}814}820}826}835}848}869}879}894}899}903}910}919}926}930}4629