Given that the base decode cache is just a hash table with no size cap and no replacements, I'd guess the hit rate is extremely high.
Even in the unlikely event that we discover the decode cache is not as effective as I believe it is, I would still encourage putting our effort into making the cache more effective and not into making the regular decoder faster. Of course, this is all based on my RISC experience... do you even use the decode cache for x86? If not, then the obvious project is to make it work for variable-length instructions. Steve On Thu, Feb 5, 2009 at 12:45 AM, Gabe Black <[email protected]> wrote: > Have we ever measured a ball park hit rate for our decode cache? I'm > wondering how much work the decoder should do to make the instructions > themselves faster and the effectiveness of the decode cache probably > plays a large role in that. > > Gabe > _______________________________________________ > m5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/m5-dev >
_______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
