llvm-svn: 100550

llvm-svn: 100549

down the set of code-completion results based on Objective-C
conventions. 

llvm-svn: 100548

llvm-svn: 100547

llvm-svn: 100546

that the integrated assembler is working.

llvm-svn: 100545

and remove assumptions about operand order

llvm-svn: 100544

allowing backend errors to be mapped through clang's 
diagnostics subsystem, including the backend location info.

We now get:

$ clang asm.c -c -o t.o -integrated-as
<inline asm>:1:2: error: unrecognized instruction
        abc incl    %eax
        ^
1 diagnostic generated.

With colors, and correct "# diagnostics generated".

llvm-svn: 100543

llvm-svn: 100542

Add a simplified constructor for clients that don't have locations
like "file not found" errors.

llvm-svn: 100538

llvm-svn: 100537

llvm-svn: 100536

presence of precompiled headers by forcibly loading all of the
methods we know about from the PCH file before constructing our
code-completion list.

llvm-svn: 100535

llvm-svn: 100534

block pointer type comparison.

llvm-svn: 100533

llvm-svn: 100532

A certain GDB testsuite case (local.cc) has a function nested inside a
class nested inside another function.  GCC presents the innermost
function to llvm-convert first.  Heretofore, the debug info mistakenly
placed the inner function at module scope.  This patch walks the GCC
context links and instantiates the outer class and function so the
debug info is properly nested.  Radar 7426545.

llvm-svn: 100530

deciding when we need to emit an extra "command failed" diagnostic.
 - This also fixes the case where we were emitting that extra diagnostics, even
   when using clang w/ the integrated assembler, which has good diagnostics.

llvm-svn: 100529

"id" or an expression of type "id". In these cases, we produce a list
of all of the (class or instance) methods, respectively, that we know about.

Note that this implementation does not yet work well with precompiled
headers; that's coming soon.

llvm-svn: 100528

llvm-svn: 100527

e.g., the right-hand side of binary expressions.

llvm-svn: 100526

llvm-svn: 100525

llvm-svn: 100521

use case where someone wants to resurrect LLVM after calling llvm_shutdown,
but I'm not aware of any clients that are affected by this.

llvm-svn: 100519

llvm-svn: 100518

Overflowing an unsigned integer is fine and behaves as you would expect.
Also fix a pasto, allowing SignExtend64 to take a 64-bit argument.

llvm-svn: 100517

This bug only shows up with GCC 4.4.1 Release-Asserts build.

llvm-svn: 100516

llvm-svn: 100515

llvm-svn: 100514

llvm-svn: 100513

llvm-svn: 100512

llvm-svn: 100511

llvm-svn: 100510

llvm-svn: 100509

llvm-svn: 100508

llvm-svn: 100506

llvm-svn: 100505

llvm-svn: 100504

diagnostic handler.

llvm-svn: 100503

llvm-svn: 100499