llvm-svn: 170225

C++11 allowed writing "vector<vector<int>>" without a space between the two ">".
This change allows this for protocols in template lists too in -std=c++11 mode,
and improves the diagnostic in c++98 mode.

llvm-svn: 170223

Targets.cpp: [cygwin] Add the predefined macro "_X86_", according to newer version of cygwin/w32api.

llvm-svn: 170188

This fixes the missing warning here:

struct S {
    template <typename T>
    void meth() {
        char arr[3];
        arr[4] = 0; // warning: array index 4 is past the end of the array
    }
};

template <typename T>
void func() {
    char arr[3];
    arr[4] = 0; // no warning
}

llvm-svn: 170180

Sema::ActOnStartOfFunctionDef is already doing.

llvm-svn: 170179

llvm-svn: 170177

llvm-svn: 170176

"entry:" is not met in -Asserts build.

llvm-svn: 170175

llvm-svn: 170170

llvm-svn: 170164

llvm-svn: 170160

I wasn't sure where to put the test case for this, but this seemed like as good
a place as any. I had to reorder the tests here to make them legible while
still matching the order of metadata output in the IR file (for some reason
making it virtual changed the ordering).

Relevant commit to fix up LLVM to actually respect 'artificial' member
variables is coming once I write up a test case for it.

llvm-svn: 170154

don't crash when loading a PCH with the older format.

The introduction of the control block broke compatibility with PCHs from
older versions. This patch allows loading (and rejecting) PCHs from an older
version and allows newer PCHs to be rejected from older clang versions as well.

rdar://12821386

llvm-svn: 170150

Patch by Martin Nowack.

llvm-svn: 170147

llvm-svn: 170143

Thanks for the -Wdocumentation catch, Dmitri!

llvm-svn: 170139

Thanks to Saleem Abdulrasool, aka compnerd!

llvm-svn: 170136

specifies not to. Dont build ASTMatchers with Rewriter disabled and
StaticAnalyzer when it's disabled.

Without all those three, the clang binary shrinks (x86_64) from ~36MB
to ~32MB (unstripped).

llvm-svn: 170135

llvm-svn: 170133

Patch by Anastasi Voitova with with small fixes by me.

llvm-svn: 170132

Patch contributed by Philip Craig!

llvm-svn: 170127

Remove little endian specification from SPIR data layout - SPIR doesn't define endiannes in the data layout.

llvm-svn: 170125

llvm-svn: 170110

bit-patterns which are not valid values for enumerated or boolean types.
These checks are the ubsan analogue of !range metadata.

llvm-svn: 170108

llvm-svn: 170100

Patch by Andrew Turner.

llvm-svn: 170096

We now check a few methods for UIResponder, NSResponder, and NSDocument.

Patch by Julian Mayer!

llvm-svn: 170089

and make sure additional uses don't get introduced.  <rdar://problem/12858424>.

llvm-svn: 170081

Sorry for the large commit, but it is much faster to convert in batches.

llvm-svn: 170067

This is a Band-Aid fix to a false positive, where we complain about not
initializing self to [super init], where self is not coming from the
init method, but is coming from the caller to init.

The proper solution would be to associate the self and it's state with
the enclosing init.

llvm-svn: 170059

to (SEL). Fixes // rdar://12859590

llvm-svn: 170058

llvm-svn: 170056

This still isn't quite right, but it fixes a crash.

I factored out findCommonParent because we need it on the result of 
getImmediateExpansionRange: for a function macro, the beginning
and end of an expansion range can come out of different
macros/macro arguments, which means the resulting range is a complete
mess to handle consistently.

I also made some changes to how findCommonParent works; it works somewhat
better in some cases, and somewhat worse in others, but I think overall
it's a better balance.  I'm coming to the conclusion that mapDiagnosticRanges
isn't using the right algorithm, though: chasing the caret is fundamentally
more complicated than any algorithm which only considers one FileID for the
caret can handle because each SourceLocation doesn't really have a single parent.
We need to follow the same path of choosing expansion locations and spelling
locations which the caret used to come up with the correct range
in the general case.

Fixes <rdar://problem/12847524>.

llvm-svn: 170049

Converts:
    LanguageExtensions
    LibASTMatchers
    LibTooling
    PCHInternals
    ThreadSanitizer
    Tooling

Patch by Mykhailo Pustovit!
(with minor edits by Dmitri Gribenko and Sean Silva)

llvm-svn: 170048

llvm-svn: 170047

llvm-svn: 170046

I don't think this will be visible just yet on <clang.llvm.org/docs/>
since I don't think that the necessary server-side setup has taken
place.

Don't shoot me over the theme. I don't want to duplicate LLVM's theme
into the clang repo at the moment, so I just used one of Sphinx's
default themes.

llvm-svn: 170042

the diagnostic has a valid location.

llvm-svn: 170040

has inconsistent ownership with the backing ivar, point the error location to the
ivar.

Pointing to the ivar (instead of the @synthesize) is better since this is where a fix is needed.
Also provide the location of @synthesize via a note.

This also fixes the problem where an auto-synthesized property would emit an error without
any location.

llvm-svn: 170039

llvm-svn: 170038