From 5440d07584e64bdd5f42d408c35df3e224bab946 Mon Sep 17 00:00:00 2001 From: lkcl Date: Tue, 10 Sep 2019 00:51:05 +0100 Subject: [PATCH] --- simple_v_extension/sv_prefix_proposal.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/simple_v_extension/sv_prefix_proposal.rst b/simple_v_extension/sv_prefix_proposal.rst index 0dff42be5..20b90744b 100644 --- a/simple_v_extension/sv_prefix_proposal.rst +++ b/simple_v_extension/sv_prefix_proposal.rst @@ -595,7 +595,7 @@ However if partial functionality is implemented, the unimplemented bits in STATE and SVPSTATE must be zero, and, in the UNIX Platform, an illegal exception **MUST** be raised if unsupported bits are written to. -SVPSTATE fields are exactly the sane layout as STATE: +SVPSTATE fields are exactly the same layout as STATE: +----------+----------+----------+----------+----------+---------+---------+ | (31..28) | (27..26) | (25..24) | (23..18) | (17..12) | (11..6) | (5...0) | @@ -603,6 +603,8 @@ SVPSTATE fields are exactly the sane layout as STATE: | rsvd | dsvoffs | subvl | destoffs | srcoffs | vl | maxvl | +----------+----------+----------+----------+----------+---------+---------+ +However note that where STATE stores the scalar register number to be used as VL, SVPSTATE.VL actually contains the actual VL value, in an identical fashion to RVV. + Additional Instructions ======================= -- 2.30.2