why the 4 spaces should be `RESERVED` even if not allocated as part
of this RFC.
+**legal, scalar and vector**
+
+| width | assembler | prefix (if any) | suffix | description |
+|-------|-----------|-----------------|-----------|---------------|
+| 32bit | fishmv | none | 0x12345678| scalar EXT0nn |
+| 64bit | sv.fishmv | 0x27000000 | 0x12345678| vector SVP64:EXT2nn |
+
+OR:
+
+| width | assembler | prefix (if any) | suffix | description |
+|-------|-----------|-----------------|-----------|---------------|
+| 64bit | fishmv | 0x24000000 | 0x12345678| scalar EXT2nn |
+| 64bit | sv.fishmv | 0x26000000 | 0x12345678| vector SVP64:EXT0nn |
+
+* 32bit fishmv EXT0nn 0x12345678 or
+ 64bit scalar EXT2nn 0x240000000 0x12345678 (typo removed)
+* vector fishmv 0x27nnnnnn 0x12345678
+
+here the encodings are the same, 0x12345678 means the same thing in both cases. (and SVP64Single, wherever it is, whenever it is).
+
+example, legal (sort-of) (edit, typo corrected)
+
+* 32bit fishmv EXT0nn 0x12345678 or
+ 64bit scalar EXT2nn 0x240000000 0x12345678
+* vector RESERVEDunallocated 0x27nnnnnn 0x12345678
+
+this is sort-of-not-illegal because the space is automatically reserved for trap-and-emulate of Vector fishmv by Lower SV Compliancy Levels.
+
+example ILLEGAL: (typo corrected)
+
+* 32bit fredmv EXT0nn 0x12345678 or
+ 64bit scalar EXT2nn 0x240000000 0x12345678
+* vector fishmv 0x27nnnnnn 0x12345678
+
+the use of 0x12345678 for fredmv in scalar but fishmv in Vector is **not** okay.
+
+another illegal example: (typo corrected)
+
+* 32bit RESERVEDunallocated EXT0nn 0x12345678 or
+ 64bit scalar EXT2nn 0x240000000 0x12345678
+* vector fishmv 0x27nnnnnn 0x12345678
+
+the fact that there does not exist a scalar variant *at all* is not okay.
\newpage{}