From 856fe5bd1cb135c39258e6ca941bf234ae63e1b1 Mon Sep 17 00:00:00 2001 From: Andrew Waterman Date: Mon, 3 Apr 2023 15:40:16 -0700 Subject: [PATCH] Delete non-normative claim that vmvr.v doesn't depend on vtype The normative text says that vmvr.v "operates as though EEW=SEW", meaning that it _does_ depend on vtype. The semantic difference becomes visible through vstart, since vstart is measured in elements; hence, how to set vstart on an interrupt, or interpret vstart upon resumption, depends on vtype. --- v-spec.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/v-spec.adoc b/v-spec.adoc index 0d1c311..ab621a7 100644 --- a/v-spec.adoc +++ b/v-spec.adoc @@ -493,7 +493,7 @@ checking for illegal values with a branch on the sign bit. If the `vill` bit is set, then any attempt to execute a vector instruction that depends upon `vtype` will raise an illegal-instruction exception. -NOTE: `vset{i}vl{i}` and whole-register loads, stores, and moves do not depend +NOTE: `vset{i}vl{i}` and whole-register loads and stores do not depend upon `vtype`. When the `vill` bit is set, the other XLEN-1 bits in `vtype` shall be