store when handling byval arguments. Thus preventing reordering of the store
with load with post-RA scheduler.

llvm-svn: 164553

llvm-svn: 164551

llvm-svn: 164550

the fact. Test cases will come when we're actually (de-)serializing
macro history.

llvm-svn: 164549

llvm-svn: 164548

This was renamed in r162632 which was badness because the C API needs to be stable.
rdar://12360096

llvm-svn: 164547

silenced by -Wno-long-long.  Thanks Richard Smith for the fix idea!

llvm-svn: 164546

> 'long long' is an extension when C99 mode is not enabled
to
> 'long long' is a C++11 extension
while compiling in C++98 mode.

llvm-svn: 164545

llvm-svn: 164544

Thanks to Byoungyoung for realizing taht we are not passing the default
option correctly.

llvm-svn: 164543

llvm-svn: 164542

(Unfortunately, I do not have a good reduced test case for this.)

llvm-svn: 164541

llvm-svn: 164540

This avoids a crash in visitAllocaInst when target data isn't available.

llvm-svn: 164539

llvm-svn: 164490

llvm-svn: 164489

[TSan] one more attempt to fix sleep_sync test: call sleep in the spawned thread so that sleep-synchronization will be detected even if child thread is started late.

llvm-svn: 164488

[TSan] Provide replacements for operators new/delete instead of declaring extern C functions with weirdly mangled names (same strategy is used in ASan).

llvm-svn: 164487

[ASan] Apply some ASan-relevant pieces of patch by Ruben Van Boxem. In the same time, remove ASan from CMake build on Windows after conversation with Timur. We don't want to support building ASan on Windows until it is in a working state.

llvm-svn: 164486

Use an explicit target to test that source fortification is off when building for Darwin with -faddress-sanitizer.

llvm-svn: 164485

StringRef makes code cleaner.  Also, make the temporary buffer smaller:
512 characters is unreasonably large for integer literals.

llvm-svn: 164484

llvm-svn: 164483

the new SROA pass. This is a benign change: the order of PHI nodes
changed.

llvm-svn: 164481

Queue the fallout. ;]

llvm-svn: 164480

integer promotion analogous to vector promotion. When there is an
integer alloca being accessed both as its integer type and as a narrower
integer type, promote the narrower access to "insert" and "extract" the
smaller integer from the larger one, and make the integer alloca
a candidate for promotion.

In the new formulation, we don't care about target legal integer or use
thresholds to control things. Instead, we only perform this promotion to
an integer type which the frontend has already emitted a load or store
for. This bounds the scope and prevents optimization passes from
coalescing larger and larger entities into a single integer.

llvm-svn: 164479

unittests/AST/StmtPrinterTest.cpp: Suppress a LP64-assumed test, "0x100000000i128 => 4294967296L", for now.

LONG_MAX is 2147483647L on common 32 bit and LLP64 (Windows x64).

llvm-svn: 164478

printing directly rather than through a complicated machinery of ObjC rewriter.

llvm-svn: 164477

Patch by Kai!

llvm-svn: 164476

across the uses of the alloca. It's entirely possible for negative
numbers to come up here, and in some rare cases simply doing the 2's
complement arithmetic isn't the correct decision. Notably, we can't zext
the index of the GEP. The definition of GEP is that these offsets are
sign extended or truncated to the size of the pointer, and then wrapping
2's complement arithmetic used.

This patch fixes an issue that comes up with *no* input from the
buildbots or bootstrap afaict. The only place where it manifested,
disturbingly, is Clang's own regression test suite. A reduced and
targeted collection of tests are added to cope with this. Note that I've
tried to pin down the potential cases of overflow, but may have missed
some cases. I've tried to add a few cases to test this, but its hard
because LLVM has quite limited support for >64bit constructs.

llvm-svn: 164475

llvm-svn: 164474

llvm-svn: 164473

llvm-svn: 164472

llvm-svn: 164471

llvm-svn: 164470

llvm-svn: 164469

llvm-svn: 164468

deprecation attribute ('deprecated', 'availability' or 'unavailable').

This warning is under a separate flag, -Wdocumentation-deprecated-sync, so it
can be turned off easily while leaving other -Wdocumentation warnings on.

llvm-svn: 164467

llvm-svn: 164466

llvm-svn: 164465

The issue is that we were calling clang_getCompletionBriefComment
unconditionally.  New we check if this function is available before calling it.

llvm-svn: 164464