| PO | 1 | 0 | !zero | nn | SVP64Single:EXT000-063 or `RESERVED4` |
| PO | 1 | 1 | nnnn | nn | SVP64:EXT000-063 |
-and reserved areas, QTY 1of 30-bit and QTY 3of 55-bit, are:
+and reserved areas, QTY 1of 32-bit, QTY 3of 30-bit and QTY 3of 55-bit, are:
| 0-5 | 6 | 7 | 8-31 | 32-3 | Description |
|-----|---|---|-------|------|---------------------------|
| PO9?| 0 | x | xxxx | 0b00 | `RESERVED2` or EXT200-216 |
| PO9?| 0 | x | xxxx | 0b01 | `RESERVED2` or EXT216-231 |
| PO9?| 0 | x | xxxx | 0b10 | `RESERVED2` or EXT232-247 |
-
-with additional potentially QTY 3of 30-bit reserved areas
-(part of Scalar Unvectoriseable EXT200-247):
-
-| 0-5 | 6 | 7 | 8-31 | 32-3 | Description |
-|-----|---|---|-------|------|---------------------------|
| PO9?| 1 | 0 | 0000 | 0b01 | RESERVED (other) |
| PO9?| 1 | 0 | 0000 | 0b10 | RESERVED (other) |
| PO9?| 1 | 0 | 0000 | 0b11 | RESERVED (other) |
* SVP64Single (`RESERVED3/4`) is *planned* for a future RFC
(but needs reserving as part of this RFC)
-* `RESERVED1/2` is available for new general-purpose **never**-Simple-V
- (non-Vectoriseable) 32-bit encodings (again, future RFCs)
+* `RESERVED1/2` is available for new general-purpose
+ (non-Vectoriseable) 32-bit encodings (other RFCs)
* EXT248-263 is for "new" instructions
- which **must** also simultaneously request the corresponding space
- in SVP64, even if the instruction is non-Vectoriseable.
+ which **must** be granted corresponding space
+ in SVP64.
* Anything Vectorised-EXT000-063 is **automatically** being
requested as 100% Reserved for every single "Defined Word"
(Public v3.1 1.6.3 definition). Vectorised-EXT001 or EXT009