Home | History | Annotate | Download | only in MCTargetDesc

Lines Matching refs:VEX

81   // In the VEX prefix, registers are seen sequencially from 0-15 and encoded
85 // VEX.VVVV => XMM9 => ~9
586 /// called VEX.
591 assert(!(TSFlags & X86II::LOCK) && "Can't have LOCK VEX.");
627 // VEX_5M (VEX m-mmmmm field):
639 // VEX_4V (VEX vvvv field): a register specifier
918 if (Encoding == X86II::VEX || Encoding == X86II::XOP) {
919 // VEX opcode prefix can have 2 or 3 bytes
936 // Can we use the 2 byte VEX prefix?
937 if (Encoding == X86II::VEX && VEX_B && VEX_X && !VEX_W && (VEX_5M == 1)) {
943 // 3 byte VEX prefix
955 && "More than 2 significant bits in VEX.m-mmmm fields for EVEX!");
1182 // It uses the VEX.VVVV field?