Corrected statement about branch count reachin 0xffff_ffff

riscv-non-isa · May 5, 2022 · 3280acd · 3280acd
1 parent 47786b8
commit 3280acd
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 1 deletion.
diff --git a/payload.tex b/payload.tex
@@ -800,7 +800,7 @@ \subsection{Format 0 \textbf{branch\_fmt} field}
 
 When a branch count is reported without an address it is because a branch has failed the prediction.  However, when an address is 
 reported along with a branch count, it will be because the packet was initiated by an uninferable discontinuity, an exception, or 
-because a branch has been encountered when \textbf{branch\_count} is 0xffff\_ffff.  For the latter case, the 
+because a branch has been encountered that increments \textbf{branch\_count} to 0xffff\_ffff.  For the latter case, the 
 reported address will always be for a branch, and in the former cases it may be.  If it is a branch, 
 it is necessary to be explicit about whether or not the prediction was met or not.  If it is met, then the reported address is 
 that of the last correctly predicted branch.

diff --git a/riscv-trace-spec.pdf b/riscv-trace-spec.pdf