Preface to Version 2.1 2026-10-20
-
Ingress Port Interface contents replaced with a reference to the RISC-V Hart to Trace Interface (RHTI) Specification, V1.0.
-
This introduces a small normative change related to multi-memory access instructions; see Ingress Port Interface for details.
-
-
Added Standard Support Packet extension, which describes the Standard Support Packet extension to Version 2.0.
-
Added Implicit Return extension, which describes the Implicit Return extension to Version 2.0.
-
Added Data Trace of Multiple-Memory Access and Compare and Swap, which describes the Data Trace of Multiple-Memory Access and Compare and Swap extension to Version 2.0.
-
Updated the decoder pseudo-code in Decoder to include support for Implicit Return, Branch Predictor and Jump Target Cache optional modes.
-
Corrections to Encoder Control: trTeInstMode hardcoded to 6 (not 7 as previously stated), trTeContext and trTeInstImplicitReturnMode changed to optional rather than not-applicable.
-
Fixed error in branch_map descriptions in tables in Format 1 introduced during earlier translation from LaTeX to asciidoc: values for branch taken or not taken were missing.
-
Added informative recommendation regarding the use of partial timestamps in packet encapsulation to Timestamping.
-
Remove historical "Future directions" chapter.
-
Minor clarifications, formatting and typo fixes.
Preface to Version 20250616
Clarifications only - no changes to normative behaviour.
-
Updated Packets and Fragments to reference the Unformatted Trace & Diagnostic Data Packet Encapsulation for RISC-V Specification;
-
Removed ambiguity between 'last' and 'final'. Last was previously used to mean both the instruction before the current one, and the final instruction traced;
-
Clarified behaviour when trace-on and trace-off triggers occur both occur in the same cycle (now in RHTI Specification);
-
Clarified that full synchronization also takes place on a privilege change (see Synchronization and Thread Address);
-
Reworded jump classifications to align with terminology used in other specifications (now in RHTI Specification);
-
Clarified when to issue sync-support packet when trace is enabled (see Format 33);
-
Clarified that branch_map can be set to 31 any time an address needs to be reported and the branch map is full (see Format 1);
-
Updated reference encoding algorithm to generalize resync behaviour and add missing trap conditions (see Algorithm);
-
Clarified that implicit returns are not stored in the jump target cache (see Jump Target Cache);
-
Updated decoder to remove ECALL, EBREAK and C.EBREAK from is_uninferrable_jump function. Including them is harmless but unnecessary, as these instrucitons don’t retire (see Decoder);
-
Corrected description of why the EPC is not always reported (see Thread Address).
-
Minor clarifications, formatting and typo fixes.
Preface to Version 20240419
Formatting and typo fixes.
Preface to Version 20240305
First version in AsciiDoc format.
Preface to Version 20231215
Clarifications only - no changes to normative behaviour.
-
Control field definitions removed from section 2, which now references the RISC-V Trace Control Interface Specification, V1.0
-
Added detail on handling of multi-load/store instructions for data trace (now in RHTI Specification).
-
Removed references to tail-calls in jump classifications (now in RHTI Specification).
-
Corrected typos where
lridwas inadvertently refered to by an earlier name (index) in Data Trace of Load/Store. -
Corrected reference decoder in Decoder to cover a corner-case related to trap returns.
Preface to Version 2.0
Ratified version of the Efficient Trace for RISC-V specification.