Displaying 2 results from an estimated 2 matches for "cr3un".
Did you mean:
cr0un
2017 Feb 10
2
generated HWEncoding based register decoders
Is there any reason why we can't generate HWEncoding based decoders for registers for mc disassemblers?
This is a concept patch to explore wether it'd work, and for my target, it does the right thing. I have one case where I have to shift a field over 2 bits, but I handle that in the glue. If I had a HWEncoding encoding on a per register class basis, I could have made it work without
2017 Feb 10
2
generated HWEncoding based register decoders
...= */ PPC::CR6,
/* [7] = */ PPC::CR7,
};
> static const unsigned CRBITRegs[] = {
> PPC::CR0LT, PPC::CR0GT, PPC::CR0EQ, PPC::CR0UN,
> PPC::CR1LT, PPC::CR1GT, PPC::CR1EQ, PPC::CR1UN,
> PPC::CR2LT, PPC::CR2GT, PPC::CR2EQ, PPC::CR2UN,
> PPC::CR3LT, PPC::CR3GT, PPC::CR3EQ, PPC::CR3UN,
> PPC::CR4LT, PPC::CR4GT, PPC::CR4EQ, PPC::CR4UN,
> PPC::CR5LT, PPC::CR5GT, PPC::CR5EQ, PPC::CR5UN,
> PPC::CR6LT, PPC::CR6GT, PPC::CR6EQ, PPC::CR6UN,
> PPC::CR7LT, PPC::CR7GT, PPC::CR7EQ, PPC::CR7UN
> };
And this:
extern const uint16_t PPCRegDecodingTable_CRBITRC[] = {
/...