Tim Hutt

> but treating it as a NOP rather than a read-zero-write-ignore register is probably wrong and likely to cause issues. Ah yes I agree - I haven't actually read the...

I'll close this for now. @maria-rehman if you have an implementation that actually does treat all unimplemented CSRs as read-only zero then feel free to make a new PR. It...

Does the WASI API actually exist yet? [Your issue about it is still open](https://github.com/WebAssembly/WASI/issues/771). Also as far as I can tell `initial_cwd()` isn't actually called from anywhere (though I may...

I'm not totally sure if we want to instead have this as part of each Sail command and use a different name for each one... But this is an improvement...

I was thinking we just have a different name for each `add_custom_command`, like `sail_smt_cache_c`, `sail_smt_cache_lean`, `sail_smt_cache_html`, `sail_smt_cache_json` etc. Some of those can run in parallel. But actually now that I...

Moved to #848.

Thinking about this more, we should probably do it by exposing a Sail function similar to `matching_pma()` to C and then calling that from `main()`.

> have types that vary depending whether that extension is present Would that require recompiling the Sail code to switch between E and not-E, because you have to include/exclude the...

It's read-only: > The "I" bit will be set for RV32I, RV64I, and RV128I base ISAs, and the "E" bit will be set for RV32E and RV64E. The Extensions field...

> My preference is that the I bit be readonly; there is no reason I can think of to switch it. I agree. Do you think you could convince them...