From dd17ec84a23363acbc1217068c153467d50d7db1 Mon Sep 17 00:00:00 2001 From: lkcl Date: Mon, 12 Sep 2022 01:57:21 +0100 Subject: [PATCH] --- openpower/sv.mdwn | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/openpower/sv.mdwn b/openpower/sv.mdwn index 1db110afd..6dd587c01 100644 --- a/openpower/sv.mdwn +++ b/openpower/sv.mdwn @@ -175,15 +175,20 @@ It requires certain guarantees to be provided. * Firstly: that instructions will never be ambiguously-defined. * Secondly, that no instruction shall change meaning to produce - different results on different hardware (present or future) -* Thirdly, that implementors are not permitted to either add + different results on different hardware (present or future). +* Thirdly, that Scalar "defined words" (32 bit instruction + encodings) if Vwctorised will also always be implemented as + identical Scalar instructions (the sole semi-exception being + Vevtorised Branch-Conditional) +* Fourthly, that implementors are not permitted to either add arbitrary features nor implement features in an incompatible way. *(Performance may differ, but differing results are not permitted)*. -* Fourthly, that any part of Simple-V not implemented by +* Fifthly, that any part of Simple-V not implemented by a lower Compliancy Level is *required* to raise an illegal - instruction trap (allowing soft-emulation). -* Fifthly, that any `UNDEFINED` behaviour for practical implementation + instruction trap (allowing soft-emulation), including if + Simple-V is not implemented at all. +* Sixthly, that any `UNDEFINED` behaviour for practical implementation reasons is clearly documented for both programmers and hardware implementors. -- 2.30.2