Tim Hutt
Tim Hutt
Note, @alasdair has demonstrated a fancier version of this with syntax highlighting and hyperlinked code (e.g. so you can click on `
There are a couple of aspects to that: 1. We obviously want to point to a *fixed* version so it is repeatable. We don't want to just always use `master`....
Mostly the `execute` clauses, but I think there are other bits too where the behaviour would be *much* clearer with the Sail code, e.g. interrupt handling: ``` /* Interrupts are...
Yeah you can, though not in this PR. E.g. for this: ``` function clause execute (UTYPE(imm, rd, op)) = { let off : xlenbits = sign_extend(imm @ 0x000); X(rd) =...
> Do you think that whenever I have that index, it would be as easy as a couple lines of code to get that Sail into the index? Yes, should...
Who do we need to review this? There's loads of scope for improvements in future but I think we need to actually start somewhere and this feels like an uncontroversial...
Rebased & updated to the `sail-riscv` 0.7 release which I just published. Are there any meetings we could add this to the agenda for?
I don't think it is anyone's specific responsibility. We should just try and get it done collaboratively in the usually open source way. I imagine it will be a relatively...
Yeah I must have made a mistake somewhere. I'll have a look.
Rebased & fixed. I think there are some further improvements that could be made. E.g. a colleague pointed out we could make an even tighter type for `VLMAX`: `range(vlen/elen, vlen)`...