diff options
| author | MITSUNARI Shigeo <[email protected]> | 2024-10-20 05:44:07 +0900 |
|---|---|---|
| committer | MITSUNARI Shigeo <[email protected]> | 2024-10-20 05:44:07 +0900 |
| commit | 8939b5a2d69f25b1598d400133740f797eebd63f (patch) | |
| tree | b1cf46881c567f028e980c00ceb68f90ebd52efb | |
| parent | 0a6ca187614a066f9c0b5ed8cf3bbb1c45f2e11a (diff) | |
| download | xbyak-8939b5a2d69f25b1598d400133740f797eebd63f.tar.gz xbyak-8939b5a2d69f25b1598d400133740f797eebd63f.zip | |
[skip ci] [doc] tweak
| -rw-r--r-- | doc/usage.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/usage.md b/doc/usage.md index b28d772..5e1946a 100644 --- a/doc/usage.md +++ b/doc/usage.md @@ -161,7 +161,7 @@ feature|AVX-VNNI-INT8, AVX512-FP16|AVX10.2 1. `vmovd` and `vmovw` instructions with REG-to-XMM or XMM-to-REG operands are always encoded using AVX10.1. When used with XMM-to-XMM operands, these instructions are always encoded using AVX10.2. -2. `vmovd` and `vmovw` instructions with MEM-to-MEM operands support multiple encoding formats, including AVX, AVX512F, AVX512-FP16, and AVX10.2. +2. `vmovd` and `vmovw` instructions with XMM-to-MEM or MEM-to-XMM operands support multiple encoding formats, including AVX, AVX512F, AVX512-FP16, and AVX10.2. Initially, I tried implementing `setDefaultEncodingAVX10` using `EvexEncoding` (resp. `VexEncoding`) instead of `AVX10v2Encoding` (resp. `EvexEncoding`). However, I abandoned this approach after discovering the complexity of the encoding requirements of `vmovd` and `vmovw`. |