Skip to content
This repository has been archived by the owner on Mar 21, 2024. It is now read-only.

Commit

Permalink
remove conflicting paragraph regarding exceptions based on vsiselect …
Browse files Browse the repository at this point in the history 
…value
  • Loading branch information
@bcstrongx
bcstrongx committed Sep 7, 2023
1 parent d7d8d28 commit 7479414
Showing 1 changed file with 0 additions and 2 deletions.
2 changes: 0 additions & 2 deletions body.adoc
View file
Original file line number Diff line number Diff line change
Expand Up @@ -223,8 +223,6 @@ The behavior upon accessing vsireg* from M-mode or HS-mode, or accessing sireg*
_It is recommended that implementations raise an illegal instruction exception for such accesses, to facilitate possible emulation (by M-mode) of these accesses._
====

The behavior upon accessing vsireg* from M-mode or HS-mode, while vsiselect holds a value that is not implemented at HS level, is UNSPECIFIED. Similarly, the behavior upon accessing sireg* (really vsireg*) from VS-mode, while vsiselect holds a value that is not implemented at VS level, is UNSPECIFIED.

Otherwise, while vsiselect holds a number in a standard-defined and
implemented range, attempts to access vsireg* from a sufficiently
privileged mode, or to access sireg* (really vsireg*) from VS-mode,
Expand Down

0 comments on commit 7479414

Please sign in to comment.