Jessica Clarke

> > This creates a nasty interaction between M-mode firmware and an S-mode OS where they both have to agree on which scheme is being used .... > > How...

If you allow non-coherent access but don't mandate that CMO be used in that case, you will end up with more platforms like the BeagleV and C906 adding in their...

Ending with a p is fine in general, it's the specific case of ending with `[0-9]p` and following it with just a major version number that's ambiguous (omitting the version...

If the canonical form of Zfoo32b + Zfoo64b is Zfoo64b only then things don't work, because then you risk a kernel or run-time linker seeing it has Zfoo64b and not...

> Hi, > > I am new to this sail-riscv project. I encountered some problems with compiling and running the elf tests. > > Initially I used `opam install sail`...

The file contents or the fact it's Isabelle is irrelevant. All it's saying is that there's a problem with the sed command being run by the Makefile. I assume you're...

I'd like to let @Alasdair look over this first given it's delving into the depths of forward and backwards mapping match functions

Sure, that's fine. I would like to see this move into the Sail runtime itself though in the long term alongside the unsigned functions, as it's much better equipped to...

Is semantic versioning really needed though? The architecture should always be backwards-compatible.

If you *just* want a way to identify whether sail-riscv A is newer than sail-riscv B, `git rev-list --first-parent --count HEAD` gives you the number of commits (excluding the right...