llvm-svn: 168387

llvm-svn: 168384

llvm-svn: 168383

llvm-svn: 168382

llvm-svn: 168380

- this commit addresses bugzilla #14385

llvm-svn: 168375

llvm-svn: 168374

llvm-svn: 168373

llvm-svn: 168372

llvm-svn: 168371

llvm-svn: 168370

[asan] pop the two internal functions from the stack trace produced by _Unwind_Backtrace (Peter Bergner)

llvm-svn: 168369

llvm-svn: 168368

[asan] don't instrument linker-initialized globals even with external linkage in -asan-initialization-order mode 

llvm-svn: 168367

[asan] make sure that linker-initialized globals (non-extern) are not instrumented even in -asan-initialization-order mode. This time with a test

llvm-svn: 168366

.git/config was marked as "bash" instead of "ini".

llvm-svn: 168365

llvm-svn: 168364

definition did.

The last part of PR14324.

llvm-svn: 168363

printing functions themselves.

Part of PR14324 (which should have just been a patch to the list, but
hey...)

llvm-svn: 168362

The issue is that we may end up with newly OOB loads when speculating
a load into the predecessors of a PHI node, and this confuses the new
integer splitting logic in some cases, triggering an assertion failure.
In fact, the branch in question must be dead code as it loads from
a too-narrow alloca. Add code to handle this gracefully and leave the
requisite FIXMEs for both optimizing more aggressively and doing more to
aid sanitizing invalid code which triggers these patterns.

llvm-svn: 168361

+ Take account of clobbers
+ Give outputs priority over inputs since they happen later.

llvm-svn: 168360

llvm-svn: 168359

llvm-svn: 168358

llvm-svn: 168357

llvm-svn: 168356

llvm-svn: 168355

When code deletes the context, the AttributeImpls that the AttrListPtr points to
are now invalid. Therefore, instead of keeping a separate managed static for the
AttrListPtrs that's reference counted, move it into the LLVMContext and delete
it when deleting the AttributeImpls.

llvm-svn: 168354

This mainly reflects the work of Tobias von Koch.

llvm-svn: 168352

llvm-svn: 168348

llvm-svn: 168347

to properly handle the combinations of these with split integer loads
and stores. This essentially replaces Evan's r168227 by refactoring the
code in a different way, and trynig to mirror that refactoring in both
the load and store sides of the rewriting.

Generally speaking there was some really problematic duplicated code
here that led to poorly founded assumptions and then subtle bugs. Now
much of the code actually flows through and follows a more consistent
style and logical path. There is still a tiny bit of duplication on the
store side of things, but it is much less bad.

This also changes the logic to never re-use a load or store instruction
as that was simply too error prone in practice.

I've added a few tests (one a reduction of the one in Evan's original
patch, which happened to be the same as the report in PR14349). I'm
going to look at adding a few more tests for things I found and fixed in
passing (such as the volatile tests in the vectorizable predicate).

This patch has survived bootstrap, and modulo one bugfix survived
Duncan's test suite, but let me know if anything else explodes.

llvm-svn: 168346

llvm-svn: 168345

llvm-svn: 168344

llvm-svn: 168343

llvm-svn: 168342

The rationale is to get YAML filenames in diagnostics from
yaml::Stream::printError -- currently the filename is hard-coded as
"YAML" because there's no buffer information available.

Patch by Kim Gräsman!

llvm-svn: 168341

llvm-svn: 168340

llvm-svn: 168339

llvm-svn: 168338

llvm-svn: 168337