llvm-svn: 154587

This fixes two crashes that appeared in case of:
  - A load of a non vectorizable type (e.g. float**)
  - An instruction that is not vectorizable (e.g. call)

llvm-svn: 154586

CompilerInstance::setCodeCompletionConsumer instead, in order to change
the SkipFunctionBodies flag accordingly. Also fixed
setCodeCompletionConsumer to take a reset() to null into account.

llvm-svn: 154585

llvm-svn: 154584

llvm-svn: 154583

turns out that it's actually needed for C++ modules support. Since simplifying
it didn't cause any test failures, I'll add a test for it.

llvm-svn: 154582

[ASan] fix output tests - r154570 changed debug info for static functions and now they are symbolized a bit differently

llvm-svn: 154581

llvm-svn: 154580

This is not quite sufficient for libstdc++'s <atomic>: we still need
__atomic_test_and_set and __atomic_clear, and may need a more complete
__atomic_is_lock_free implementation.

We are also missing an implementation of __atomic_always_lock_free,
__atomic_nand_fetch, and __atomic_fetch_nand, but those aren't needed
for libstdc++.

llvm-svn: 154579

FunctionDecl::Create calls as well.

rdar://11079003

llvm-svn: 154578

They reference the PC directly, so things work properly that way.

rdar://11231229

llvm-svn: 154576

rdar://problem/11031264

llvm-svn: 154573

rdar://11079003

llvm-svn: 154571

The mangler doesn't like non-prototyped functions so only use a mangled
name for prototyped functions.

rdar://11079003

llvm-svn: 154570

so.

llvm-svn: 154569

get the diagnostic category name from a serialized diagnostic when the version of libclang used
to read the diagnostic file is newer than the clang that emitted the diagnostic file.

llvm-svn: 154567

of a __block struct object. // rdar://11230308

llvm-svn: 154566

Add test for a construct we currently reject, constant-evaluating a load from a constant string.  Given that gcc doesn't accept this, we should continue to not accept it, even though it was accidentally supported by clang for a brief period.

llvm-svn: 154564

llvm-svn: 154563

llvm-svn: 154547

otherwise expand FNEG during legalization.

llvm-svn: 154546

Invalid operation is signaled if the operand of these instructions is NaN.

llvm-svn: 154545

of a VST instruction.

llvm-svn: 154544

llvm-svn: 154543

As per Jordy's review. Creating a symbol here is more flexible; however
I could not come up with an example where it was needed. (What
constrains can be added on of the symbol constrained to 0?)

llvm-svn: 154542

symbolic regions would help.

Thanks to Richard Smith.

llvm-svn: 154541

- FCOPYSIGN nodes that have operands of different types were not handled.
- Different code was generated depending on the endianness of the target.

Additionally, code is added that emits INS and EXT instructions, if they are
supported by target (they are R2 instructions).

llvm-svn: 154540

Objective-C class doesn't have a definition but
Clang tries to read through its protocols anyway.

llvm-svn: 154538

llvm-svn: 154535

first ivar in the list is a bitfield.
// rdar://11229770

llvm-svn: 154534

llvm-svn: 154533

llvm-svn: 154532

llvm-svn: 154531

right place to pick up parsing. In C++, this had a tendency to skip everything
declared within headers if the TU starts with garbage.

llvm-svn: 154530

llvm-svn: 154527

llvm-svn: 154526

llvm-svn: 154525

to get at the parameters (and their types) of a function or objc method cursor.

int clang_Cursor_getNumArguments(CXCursor C);
CXCursor clang_Cursor_getArgument(CXCursor C, unsigned i);

rdar://11201527

llvm-svn: 154523

llvm-svn: 154522

Per discussion with Howard, we are not interested in maintaining
compatibility with older versions of clang.

All tests pass with ToT clang, except for two which assert due to
a pre-existing, unrelated bug.

llvm-svn: 154521