Tags: libriscv/libriscv
Tags
Fix DecoderCache needs to be zeroed with binary translation Long-running applications continously re-use memory, and when binary translation is loadable it pre-populates the decoder cache with entries. A dirty decoder cache can potentially lead to the decoder finding wrong bintr entries, which can lead to rare jumps that don't lead to any productive execution. It may even loop forever since the binary translation will not find an entry for the current PC, return back, and then the wrong entry jumps right back. Let's just zero the whole decoder cache to begin with. I chose to always zero regardless of binary translation settings, just in case.
PreviousNext