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 
abstract base class MCDisassembler (llvm/MC/MCDisassembler.h).

The disassembler is documented in detail in

- lib/Target/X86/Disassembler/X86Disassembler.cpp (disassembler runtime)
- utils/TableGen/DisassemblerEmitter.cpp (table emitter)

You can test the disassembler by running llvm-mc -disassemble for i386
or x86_64 targets.  Please let me know if you encounter any problems
with it.

llvm-svn: 91749

llvm-svn: 91741

llvm-svn: 91718

This works now: (set_option "list_opt", ["val_1", "val_2", "val_3"])

llvm-svn: 91679

llvm-svn: 91594

llvm-svn: 91593

llvm-svn: 91592

llvm-svn: 91554

llvm-svn: 91552

llvm-svn: 91463

llvm-svn: 91458

llvm-svn: 91448

llvm-svn: 91442

llvm-svn: 91420

llvm-svn: 91419

Checks that the code generated by 'tblgen --emit-llvmc' can be actually
compiled. Also fixes two bugs found in this way:

- forward_transformed_value didn't work with non-list arguments
- cl::ZeroOrOne is now called cl::Optional

llvm-svn: 91404

llvm-svn: 91402

llvm-svn: 91379

characters in them, in which case the grep will just return 'Binary file
matches' and the whole thing falls over.

llvm-svn: 91302

llvm-svn: 91301

llvm-svn: 90934

llvm-svn: 90871

llvm-svn: 90785

llvm-svn: 90784

Use 'forward_values' + 'comma_separated' instead.

llvm-svn: 90774

llvm-svn: 90770

llvm-svn: 90764

llvm-svn: 90628

llvm-svn: 90599

llvm-svn: 90214

llvm-svn: 90189

llvm-svn: 90065

llvm-svn: 89833

llvm-svn: 89729

Note that "hasDotLocAndDotFile"-style debug info was already broken;
people wanting this functionality should implement it in the
AsmPrinter/DwarfWriter code.

llvm-svn: 89711

good nearby fuzzy match. Frequently the input is nearly correct, and just
showing the user the a nearby sensible match is enough to diagnose the problem.
 - The "fuzzyness" is pretty simple and arbitrary, but worked on my three test
   cases. If you encounter problems, or places you think FileCheck should have
   guessed but didn't, please add test cases to PR5239.

For example, previously FileCheck would report this:
--
t.cpp:21:55: error: expected string not found in input
// CHECK: define void @_Z2f25f2_s1([[i64_i64_ty]] %a0)
                                                      ^
<stdin>:19:30: note: scanning from here
define void @_Z2f15f1_s1(%1) nounwind {
                             ^
<stdin>:19:30: note: with variable "i64_i64_ty" equal to "%0"
--

and now it also reports this:
--
<stdin>:27:1: note: possible intended match here
define void @_Z2f25f2_s1(%0) nounwind {
^
--

which makes it clear that the CHECK just has an extra ' %a0' in it, without
having to check the input.

llvm-svn: 89631

additional information about the current definitions of the variables used in
the string.

llvm-svn: 89628

separate character.
 - Chris, OK?

llvm-svn: 89626

llvm-svn: 89582

values, resolving references to them, and then removing the definitions.
If a template argument is set to an undefined value, we need to resolve
references to that argument to an explicit undefined value.  The current code
leaves the reference to the template argument as it is, which causes an
assertion failure later when the definition of the template argument is
removed.

llvm-svn: 89581