Christian Herber
Christian Herber
is there anything happening on this one?
> I still see this mistake in online documentation dito. would be good to get fixed so not everybody has to stumble over this.
I tried to list the relevant changes in the changelog of the v1.0.0-rc.1 release. Tag core-v-xif_v0.2.0 is equivalent to v0.2.0 with the only difference that v0.2.0 has a fixed build....
I see. It is also here in the html: https://docs.openhwgroup.org/projects/openhw-group-core-v-xif/en/latest/preface.html#changelog No idea why sphinx does not pick that up for the pdf version. Seems to be a limitation in Sphinx....
Created this ticket https://github.com/ewjoachim/sphinx-github-changelog/issues/122
> Alternatively, this could be written in section 3.1 History. We can write a manual changelog, that wouldn't be an issue. But the point is to have no duplication of...
the current model is that illegal instruction traps must be indicated by not accepting the instruction. For performant implementations, this does indeed require the decision to be quick (usually single...
to add to this: the exceptions are only there for the memory interface. RISC-V unprivileged extensions do not raise any exceptions outside of illegal instruction if they do not do...
This would be great input. For which CPU and coprocessor would that be?