- The difference from getASTObjCInterfaceLayout is that the computes
   the layout including synthesized ivars.

 - No functionality change, they currently both compute the same thing
   -- whether that includes synthesized ivars or not depends on when
   they get called!!!

llvm-svn: 70690

llvm-svn: 70689

 - This is somewhat cleaner and also fixes PR4063 for real, I had the
   order wrong so we were just creating an empty dependency file.

llvm-svn: 70687

llvm-svn: 70686

this fixes http://llvm.org/bugs/show_bug.cgi?id=3373#c20

llvm-svn: 70685

llvm-svn: 70684

llvm-svn: 70683

-Create DebugLocs without the need to have a DwarfWriter around

llvm-svn: 70682

llvm-svn: 70681

llvm-svn: 70680

from the asm string, but reject references to the smaller one.

llvm-svn: 70679

llvm-svn: 70678

the input.  This is part of PR3373.

llvm-svn: 70677

llvm-svn: 70676

like bitfields.  incidentally llvm-gcc crashes on this sort of thing also. :)

llvm-svn: 70675

 - No functionality change.

llvm-svn: 70674

llvm-svn: 70673

llvm-svn: 70672

processing the outputs, no functionality change.

llvm-svn: 70671

number is not mentioned in the asm string, let it past sema. 
Right now these are currently rejected by the llvm code generator
but this will be fixed next.

llvm-svn: 70670

if there is an input constraint that is tied to it.

llvm-svn: 70669

promotions.  This should be fixed by not modeling asm operands (which 
require the ()'s according to the grammar) as not being paren exprs.

llvm-svn: 70668

Fix: <rdar://problem/6850275> CF objects returned from methods with "new" or "copy" in their name should be treated as owned

For methods that follow the "fundamental rule" and return Core
Foundation objects, treat those objects as owned by the caller.

llvm-svn: 70665

llvm-svn: 70664

llvm-svn: 70663

no functionality change.

llvm-svn: 70662

llvm-svn: 70661

Convert ArgEffects from an std::vector to an ImmutableMap.  This will make it much easier to clean up the summary generation logic with annotations.

llvm-svn: 70660

llvm-svn: 70659

reason for adding these is to error out in CodeGen when trying to generate
them instead of silently emitting a call to a non-existent function.

(Note that it is not valid to lower these to setjmp/longjmp; in addition 
to that lowering being different from the intent, setjmp and longjmp 
require a larger buffer.)

llvm-svn: 70658

llvm-svn: 70657

fix-it hint is much worse than no fix-it hint. (Fixes PR4084).

When we need to truncate a source line to fix in the terminal, make
sure to take the width of the fix-it information into account, too.

llvm-svn: 70656

show an ellipsis where we have removed text. An example:

/Users/dgregor/Projects/llvm/tools/clang/test/Misc/message-length.c:18:120:
warning: 
      comparison of distinct pointer types ('int *' and 'float *')
  ...a_func_to_call(ip == FloatPointer, ip[ALongIndexName], ...
                    ~~ ^  ~~~~~~~~~~~~

llvm-svn: 70655

word-wrapping by default in Emacs; yay!). Thanks, Daniel.

Use LLVM's System layer rather than calling isatty() directly.

Fix a thinko in printing the indentation string that was causing some
weird output.

llvm-svn: 70654

them to bool.

llvm-svn: 70653

an interface.

llvm-svn: 70652

simplify the retrieve logic.

llvm-svn: 70651

llvm-svn: 70650

llvm-svn: 70649

 - In particular, don't forward them to gcc; these participate in the
   selection of the tool chain, which should know how to talk to gcc
   and be fixed if it doesn't.

llvm-svn: 70648