You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the current PDF file name of the E-Trace Spec is "riscv-trace-spec.pdf". The problem with this name is that:
This name is not distinguishable from N-Trace.
This name is not aligned with the file names of the other trace specs.
My suggestion would be to rename it to "RISC-V-E-Trace.pdf" (to align it with RISC-V-N-Trace.pdf, RISC-V-Trace-Connectors.pdf, RISC-V-Trace-Control-Interface.pdf).
I vaguely remember that in the past there was the argument that there are fixed links in other places that link to riscv-trace-spec.pdf, and that this can not easily be changed. But where are these links?
I'd prefer if we keep the name riscv-trace-spec, but incorporate all of the trace specs within it. That way there is one comprehensive non-ISA spec that includes all components of RISC-V trace, including chapters on the interface, connectors, and each trace format, but without all the duplication (e.g., itype definitions) that is currently required in the separate specs.
Hi,
the current PDF file name of the E-Trace Spec is "riscv-trace-spec.pdf". The problem with this name is that:
My suggestion would be to rename it to "RISC-V-E-Trace.pdf" (to align it with RISC-V-N-Trace.pdf, RISC-V-Trace-Connectors.pdf, RISC-V-Trace-Control-Interface.pdf).
I vaguely remember that in the past there was the argument that there are fixed links in other places that link to riscv-trace-spec.pdf, and that this can not easily be changed. But where are these links?
On the GitHub page https://github.com/riscv-non-isa/riscv-trace-spec I can not find any "riscv-trace-spec.pdf" (any more?) that could be linked to.
Also, https://wiki.riscv.org/display/HOME/RISC-V+Technical+Specifications uses a Google drive link, which probably changes each time that we upload a new file version (or does it not?).
Thanks,
Markus
The text was updated successfully, but these errors were encountered: