in ObjCMethods.

Extend FunctionTextRegion to represent ObjC methods as well as
functions. Note, it is not clear what type ObjCMethod region should
return. Since the type of the FunctionText region is not currently used,
defer solving this issue.

llvm-svn: 164046

Retain cycles happen in the case where a block is persisted past its
life on the stack, and the way that occurs is by copying the block.
We should thus look through any explicit copies we see.

Note that Block_copy is actually a type-safe wrapper for _Block_copy,
which does all the real work.

<rdar://problem/12219663>

llvm-svn: 164039

llvm-svn: 164033

Fixes http://code.google.com/p/address-sanitizer/issues/detail?id=113

llvm-svn: 164031

llvm-svn: 164028

llvm-svn: 163994

headers and modules in more detail. I'd still like to expand on some
of the modules-related issues further, but this is a decent start.

llvm-svn: 163989

declaration for the entity being documented.

llvm-svn: 163986

'function-like' type that can be annotated with \param.

Thanks to Eli Friedman for noticing!

llvm-svn: 163985

llvm-svn: 163983

llvm-svn: 163982

UnqualifiedId() properly noncopyable.

llvm-svn: 163981

llvm-svn: 163980

llvm-svn: 163966

C11 7.17's atomic operations. GNU's __atomic_* builtins do allow const-qualified
atomics, though (!!) so don't restrict those.

llvm-svn: 163964

It's not clear if this is working yet on the buildbot.  Reverting until we have
time to investigate.

llvm-svn: 163963

Specifically, this should warn:

  __block block_t a = ^{ a(); };

Furthermore, this case which previously warned now does not, since the value
of 'b' is captured before the assignment occurs:

  block_t b; // not __block
  b = ^{ b(); };

(This will of course warn under -Wuninitialized, as before.)

<rdar://problem/11015883>

llvm-svn: 163962

an environment variable for debugging purposes.

llvm-svn: 163958

llvm-svn: 163941

bytes of the buffer and not the size of the string, otherwise we
may overwrite the buffer if there is a mismatch between the size
of the string and the CharByteWidth, and assertions are disabled.

The bug where this could occur was fixed in r163931.
Related to rdar://12069503

llvm-svn: 163939

to the target info.

Related to rdar://12069503.

llvm-svn: 163931

of a build without needing to use ccc-analyzer.

llvm-svn: 163927

We need the clang executable to print the list of available checkers.

llvm-svn: 163925

change (the problematic cases in ParseDecl.cpp are currently impossible).

llvm-svn: 163920

When diagnosing multiple mem-initializers in a delegating ctor, point to the delegating initializer, not to the first initializer. For good measure, also highlight the other initializer.

llvm-svn: 163919

llvm-svn: 163918

// rdar://10554025

llvm-svn: 163917

llvm-svn: 163914

llvm-svn: 163910

since no Doxygen command starts with a digit.

llvm-svn: 163909

llvm-svn: 163905

paths when target is MIPS 32-bit.

The patch reviewed by Chandler Carruth.

llvm-svn: 163898

llvm-svn: 163874

without a cast. Fixes <rdar://problem/11830912>.

llvm-svn: 163873

type checking for non-static data member initializers in a dependent
class, because our ASTs lose too much information to when
type-checking an initializer. Fixes <rdar://problem/11974632>,
although the result is still rather unsatisfactory.

llvm-svn: 163871

llvm-svn: 163870

both a virtual and a non-virtual offset. PR13832.

llvm-svn: 163866

llvm-svn: 163865

llvm-svn: 163863

ivar and property references as member accesses and produce the actual
type of the declaration. Fixes <rdar://problem/12031582>.

llvm-svn: 163858