Hi Gabe,
It's been a really long time since I've looked at this, but the idea of
generalizing the notion of bitfield to include pieces of decoder state as
well as instruction fields makes sense to me. The free-form string
solution seems reasonable as well... much lighter weight than declaring a
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
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
