Skip to content

Commit

Permalink
Merge pull request #171 from riscv-non-isa/updates-2.0.4-Issues-169
Browse files Browse the repository at this point in the history
Clarify which addresses are stored in the JTC - Issue 169
  • Loading branch information
IainCRobertson authored Feb 18, 2025
2 parents 045e6af + 161b693 commit 4bf513c
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions branchTrace.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -331,12 +331,12 @@ cache with identical behavior will need to be implemented in the decoder
software. Even a small cache can provide significant improvement.

The cache shall comprise 2^_cache_size_p_^ entries, each of which can
contain an instruction address. It will be direct mapped, with each
contain an instruction address. The addresses stored in the cache are
the targets of uninferable jumps. It will be direct mapped, with each
entry indexed by bits _cache_size_p_:1 of the instruction address (or
__cache_size_p__+1:2 if compressed instructions aren't supported).

Each uninferable jump target is first compared with the entry at its
index in the cache. If it is found in the cache, the index number is
Each uninferable jump target is first compared with the entry in the cache at the index derived from the jump target address. If it is found in the cache, the index number is
traced rather than the target address. If it is not found in the cache,
the entry at that index is replaced with the current instruction
address.
Expand Down

0 comments on commit 4bf513c

Please sign in to comment.