Tim Hutt
Tim Hutt
Yeah I think you want to do something like this (with a hypothetical `read()` function that handled CHERI etc. ``` match read(rs1, imm, WORD) { Ok(val_0) => { match read(rs1,...
I was imagining that we wouldn't internal the entire AST, more something along the lines of [@ThinkOpenly 's json backend](https://github.com/ThinkOpenly/sail/tree/json)... but instead of hard-coding `"encdec"` etc. for the Sail model,...
> Would merging the backend into the canonical Sail repo alleviate the concern with AST drift? I think that would make sense, but it would have to lose all the...
I think I didn't explain what I meant very well. We could have an architecture-agnostic backend that extracted information from model into an "unfriendly" JSON file, and then an architecture-specific...
No worries! Maybe we can do it more gradually as we fix the types.
3 was discussed in the meeting. @Alasdair prefers to change `physaddr`/`virtaddr` case to be `Physaddr` etc. so we'll do that instead.