From 6282f808fc3197da0fce8503380136c4c81cd5f7 Mon Sep 17 00:00:00 2001 From: Luke Kenneth Casson Leighton Date: Mon, 30 Apr 2018 14:15:34 +0100 Subject: [PATCH] clarify --- isa_conflict_resolution/mvendor_march_warl.mdwn | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/isa_conflict_resolution/mvendor_march_warl.mdwn b/isa_conflict_resolution/mvendor_march_warl.mdwn index 96445eb7e..01c1969ad 100644 --- a/isa_conflict_resolution/mvendor_march_warl.mdwn +++ b/isa_conflict_resolution/mvendor_march_warl.mdwn @@ -38,11 +38,19 @@ mvendorid-marchid tuple shall have the effect of *purely* disabling certain instruction encodings and enabling others. Note also that during (for example) standard OS context-switching *all* -state of *all* extensions (and variants of the Base Standards) related +state of *all* enabled extensions (and variants of the Base Standards) related to *all* mvendorid-marchid tuples will need to be saved onto the stack, given that a hart may, at any time, switch between any available mvendorid-marchid tuples. +In other words there is absolutely zero connection *of any kind whatsoever* +between the "encoding switching" and the state or status of the Extensions +that the binary encodings are being directed *at* (on any upcoming +conflicting instruction encodings). If a program requires the enablement +or disablement of an Extension it **uses MISA and other official methods +to do so** that have **absolutely nothing to do with what mvendorid-marchid +is presently enabled**. + ## Compliance It was pointed out early in the discussions that Compliance Testing may -- 2.30.2