[gem5-dev] Decoding using decoder state

In the x86 decoder, some architectural state (CPU mode, a couple other things) is used to pick an active decode cache from a hash map of caches. That state could then be used when decoding instructions since we'd still always get the same thing for a particular ExtMachInst given a particular

[gem5-dev] Cron m5test@zizzer /z/m5/regression/do-regression quick

scons: *** [build/ALPHA_MOESI_hammer/gem5.opt] Error 1 * build/ALPHA/tests/opt/quick/se/00.hello/alpha/linux/simple-timing passed. * build/ALPHA/tests/opt/quick/se/00.hello/alpha/tru64/simple-timing-ruby passed. * build/ALPHA/tests/opt/quick/se/01.hello-2T-smt/alpha/linux/o3-timing

Re: [gem5-dev] Decoding using decoder state

I realize the context for this might not be something everybody is familiar with. If you need me to explain what this is about more I can do that. Gabe On Wed, Feb 4, 2015 at 2:23 PM, Gabe Black gabebl...@google.com wrote: In the x86 decoder, some architectural state (CPU mode, a couple other

[gem5-dev] Review Request 2627: Ruby: Update backing store option to propagate through to all RubyPorts

--- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/2627/ --- Review request for Default. Repository: gem5 Description --- Changeset