EVEX & VEX : operands encoding

Intel® ISA Extensions

Use hardware-based isolation and memory encryption to provide more code protection in your solutions.

EVEX & VEX : operands encoding

1,611 Views

Hi,

I have a question about EVEX encoding and more precisely, about operands encoding with EVEX present (SIB, VSIB, EVEX.vvvv, ModR/M). According to https://en.wikipedia.org/wiki/EVEX_prefix,

Four bits R, X, B, and W from the REX prefix. W expands the operand size to 64 bits or serves as an additional opcode, R expands reg, B expands r/m or reg, and X and B expand index and base in the SIB byte. Comparing to the VEX prefix, RXB are provided in non-inversed forms, just like in the REX prefix.

1. Does it mean EVEX.R, EVEX.B, EVEX.X must be used without any 1's complement (while 1's complement is applyed on VEX.RBX) ?

2. Is there any "official" documentation about this ?

3. What about EVEX.V' ? Must we apply a 1's complement ?

Thanks

Link Copied

0 Replies

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.