BarebitOpenSource

Results 53 comments of BarebitOpenSource

Potential missing metadata attribute for REX.W prefix and no prefix needed

Idea: reuse `pref` element with new `REXW` pseudoconstant. The `REXW` doesn't mean value 0x48 but only the `W` bit in REX, if REX is present.

Potential missing metadata attribute for REX.W prefix and no prefix needed

It seems that because of AVX `VZEROUPPER` vs. `VZEROALL`, there will be an attribute indicating dependency on `VEX.L` because it is not possible to indicate it using operand type. To...

Potential missing metadata attribute for REX.W prefix and no prefix needed

Related missing instructions: `XSAVEOPT`, `XSAVEOPT64` `XSAVES`, `XSAVES64`

Potential missing metadata attribute for REX.W prefix and no prefix needed

Moved to https://github.com/mazegen/x86reference/issues/15

MOVSLDUP use wrong operand types

Good point. I need to figure out why Intel uses this operand type in the manual.

MOVSLDUP use wrong operand types

Won't fix, see #27.

MOVSHDUP use wrong operand types

Good point. I need to figure out why Intel uses this operand type in the manual. Edit: see Core 2 manual, revision 028, 253667.pdf, opcode map.

MOVSHDUP use wrong operand types

I have reviewed it and I decided to keep it as it is. All the old Intel manuals consistently indicate the operands as `MOVSHDUP Vq, Wq`. Also the `VMOVSHDUP` operands...

MOVSHDUP use wrong operand types

Added to the main README.

UNPCKHPS use wrong operand types

Good point. I need to figure out why Intel uses this operand type in the manual.