search for: finstructions

.... 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 be quite large. - numberedInstructions in X86DisassemblerEmitter.cpp is not a good candidate because there are upwards of a thousand instructions in the x86 table. - fInstructionSpecifi...

Hi Sean, > 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

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