Following ARC feedback, moved compressed encodings into separate exte…

…nsion

- preliminary name Zcmlsd
- depends on Zilsd and Zca
- incompatible with Zcf

header.adoc

@@ -1,8 +1,8 @@
 [[header]]
 :description: Load/Store Pair (LSP) instructions
 :company: RISC-V.org
-:revdate: 12/2023
-:revnumber: 0.8.1-draft
+:revdate: 04/2024
+:revnumber: 0.8.2-draft
 :revremark: This document is in Frozen state. See http://riscv.org/spec-state for details.
 :url-riscv: http://riscv.org
 :doctype: book
@@ -36,7 +36,7 @@ endif::[]
 :footnote:
 :xrefstyle: short
 
-= Load/Store Pair for RV32 (Zilsd)
+= Load/Store Pair for RV32 (Zilsd & Zcmlsd)
 
 // Preamble
 [WARNING]
@@ -53,7 +53,7 @@ Attribution 4.0 International License (CC-BY 4.0). The full
 license text is available at
 https://creativecommons.org/licenses/by/4.0/.
 
-Copyright 2023 by RISC-V International.
+Copyright 2023-2024 by RISC-V International.
 
 [preface]
 === Contributors
@@ -62,7 +62,8 @@ Christian Herber, Torbjørn Viem Ness, Tariq Kurd.
 
 == Introduction
 
-Zilsd is an RV32-only extension, which adds load and store instructions using register pairs. I does so by reusing existing instruction encodings which are RV64-only.
+This specification contains two RV32-only extensions, which add load and store instructions using register pairs. It does so by reusing existing instruction encodings which are RV64-only. 
+The specification defines 32-bit encodings (Zilsd extension) and 16-bit encodings (Zcmlsd).
 
 Load and store instructions will use the same definition of even-odd pairs as layed out in Zdinx.
 

zilsd.adoc

@@ -1,5 +1,5 @@
 [[chapter2]]
-== Load/Store pair instructions
+== Load/Store pair instructions (Zilsd)
 
 The Zilsd extension provides load/store pair instructions for RV32 analogous to the existing RV64 doubleword load/store instructions. The existing RV64 encodings are reused, which are reserved in RV32 without this extension.
 
@@ -19,9 +19,11 @@ The Zilsd extension adds the following RV32-only instructions:
 Implementations may need to crack these instructions, and perform to memory operations in sequence. Therefore, implementations are not required to ensure atomicity when storing to memory. Still, writing to the individual registers relating to a 64-bit operand of a load must happen atomically to ensure fault handling is possible.
 ====
 
-=== Compressed Load/Store pair instructions
+=== Compressed Load/Store pair instructions (Zcmlsd)
 
-If the C extension is present and F is not present, Zilsd adds the following RV32-only instructions:
+Zcmlsd depends on Zilsd and Zca. I has overlapping encodings with Zcf and is thus incompatible with F. 
+
+Zcmlsd adds the following RV32-only instructions:
 
   - C.LDSP loads stack-pointer relative 64-bit value into registers `rd'` and `rd'+1`. It computes its effective address by adding the zero-extended offset, scaled by 8, to the stack pointer, `x2`. It expands to `ld rd, offset(x2)`. C.LDSP is only valid when _rd_≠x0; the code points with _rd_=x0 are reserved.
   - C.SDSP stores a stack-pointer relative 64-bit value from registers `rs2'` and `rs2'+1`. It computes an effective address by adding the _zero_-extended offset, scaled by 8, to the stack pointer, `x2`. It expands to `sd rs2, offset(x2)`.
@@ -32,8 +34,6 @@ If the C extension is present and F is not present, Zilsd adds the following RV3
   It computes an effective address by adding the zero-extended offset, scaled by 8, to the base address in register rs1'.
   It expands to `sd rs2', offset(rs1')`.
 
-These instructions are mutually exclusive with Zcf.
-
 === Use of x0 as operand
 
 LD instructions with destination `x0` are processed as any other load, but the result is discarded entirely. Specifically, a load pair to `x0` does not cause `x1` to be written. For C.LDSP, usage of `x0` as the destination is reserved.