Tariq Kurd

I've done some cleanup of the text (no spec changes). Is the intention for _all_ cores to have this? So we'll need to have this on the application cores as...

https://github.com/riscv/riscv-cheri/pull/232 we settled on `integer pointer` and `capability pointer` mode as they are the most descriptive.

We know that `c` is wrong - but we're hoping to get an official letter allocated. Whatever we call it will be changed again so I don't see a strong...

I think that `menvcfg` should also get the CW, CRG bits, otherwise this scheme is different to how the other bit-fields work where `menvcfg` is a superset.

> > I think that `menvcfg` should also get the CW, CRG bits, otherwise this scheme is different to how the other bit-fields work where `menvcfg` is a superset. >...

> it's probably worth adding something about the benefits/consequences of each of the 4 options, but I think the actual spec is ok now Jon has pointed out that this...

> > (v)sstatus would make the most sense for it. There's precedent from SUM and MXR (and TVM in the full mstatus). > > @jrtc27 I agree that (v)sstatus would...

> It needs to be in `mstatus` because it is a superset of `sstatus`. Here is the relevant fragment form the privileged spec > yes ok - but I noticed...

any objections to merging this?

oh I see, I thought we were talking about both. Probably better resolve this one next! I'm not keen on integer mode, as it also does FP, Vector etc. so...