search for: foperands

...changing the return to "-1U" to make it explicit. 6. The use of "#include <iostream>" is strictly forbidden. Please remove it wherever you find it (HexDisassembler.h for one). 7. Look for opportunities to use the LLVM small container classes. For instance, the "fOperands" ivar in RecognizableInsn. 8. While we're on that, please use "Instruction" or "Instr" instead of "Insn" for consistency's sake. 9. You have types called "operandType_t", etc. We normally don't use the "_t" suffix for types. P...

Dear mailing list: the attached diff implements a table-driven disassembler for the X86 architecture (16-, 32-, and 64-bit incarnations), integrated into the MC framework. The disassembler is table-driven, using a custom TableGen backend to generate hierarchical tables optimized for fast decode. The disassembler consumes MemoryObjects and produces arrays of MCInsts, adhering to the

...ude <iostream>" is strictly forbidden. Please > remove it wherever you find it (HexDisassembler.h for one). Yeah, I guess those static initializers aren't so great. Removed. > 7. Look for opportunities to use the LLVM small container classes. > For instance, the "fOperands" ivar in RecognizableInsn. I looked at my uses of std::vector but they wouldn't really benefit from the good performance of SmallVector for small values of N. - fInstructions in X86Disassembler.h is not a good candidate for this, because the number of instructions could potentially b...