Displaying 3 results from an estimated 3 matches for "x86disassembleremitt".
Did you mean:
x86disassembleremitter
2009 Aug 18
2
[LLVMdev] X86 Disassembler
...ed for fast
decode. The disassembler consumes MemoryObjects and produces arrays
of MCInsts, adhering to the abstract base class MCDisassembler (llvm/
MC/MCDisassembler.h).
The disassembler is documented in detail in
–
- lib/Target/X86/X86Disassembler.h (disassembler runtime)
- utils/TableGen/X86DisassemblerEmitter.h (table emitter)
–
as well as in the individual files, functions, and classes.
I implemented a use case in tools/llvm-mc/HexDisassembler.cpp, which
implements an interactive disassembler for sequences of bytes entered
in hex on standard input. Example output:
–
localhost:llvm spyffe$ ./Deb...
2009 Aug 18
0
[LLVMdev] X86 Disassembler
...mbler consumes MemoryObjects and produces arrays
> of MCInsts, adhering to the abstract base class MCDisassembler (llvm/
> MC/MCDisassembler.h).
>
> The disassembler is documented in detail in
> –
> - lib/Target/X86/X86Disassembler.h (disassembler runtime)
> - utils/TableGen/X86DisassemblerEmitter.h (table emitter)
> –
> as well as in the individual files, functions, and classes.
>
> I implemented a use case in tools/llvm-mc/HexDisassembler.cpp, which
> implements an interactive disassembler for sequences of bytes
> entered in hex on standard input. Example output:
&...
2009 Aug 19
3
[LLVMdev] X86 Disassembler
...within a .cpp
> file, go ahead and define it in an anonymous namespace and mark it
> "VISIBILITY_HIDDEN". Like this:
>
> namespace {
> class VISIBILITY_HIDDEN StringMemoryObject : public MemoryObject {
> ...
I used VISIBILITY_HIDDEN for both StringMemoryObject and
X86DisassemblerEmitter::X86DEBackend.
I wrapped StringMemoryObject in an anonymous namespace.
I didn't wrap X86DEBackend because it's already nested.
> 5. In "readBytes" in StringMemoryObject, you're returning a "-1",
> but the method's return type is "uint64_t". D...