llvm-svn: 205702

llvm-svn: 205627

llvm-svn: 205623

we've seen a flake on this test
next time it happens we will be able to gather some info

llvm-svn: 205619

This reduces .tbss from 109K down to almost nothing.

llvm-svn: 205618

[asan] fix a leak in __tls_get_addr handler; introduce a run-time flag to disable this handler completely; remove a workaround for a bug fixed in glibc

llvm-svn: 205617

llvm-svn: 205614

llvm-svn: 205613

If a multi-threaded program calls fork(), TSan ignores all memory accesses
in the child to prevent deadlocks in TSan runtime. This is OK, as child is
probably going to call exec() as soon as possible. However, a rare deadlocks
could be caused by ThreadIgnoreBegin() function itself.

ThreadIgnoreBegin() remembers the current stack trace and puts it into the
StackDepot to report a warning later if a thread exited with ignores enabled.
Using StackDepotPut in a child process is dangerous: it locks a mutex on
a slow path, which could be already locked in a parent process.

The fix is simple: just don't put current stack traces to StackDepot in
ThreadIgnoreBegin() and ThreadIgnoreSyncBegin() functions if we're
running after a multithreaded fork. We will not report any
"thread exited with ignores enabled" errors in this case anyway.

Submitting this without a testcase, as I believe the standalone reproducer
is pretty hard to construct.

llvm-svn: 205534

llvm-svn: 205531

llvm-svn: 205418

llvm-svn: 205417

It does not do what it's name says, and what it actually does is hard to
describe, and is not useful at all.

llvm-svn: 205415

An assert()-like function that checks that a memory range is fully initialized.

llvm-svn: 205413

llvm-svn: 205412

llvm-svn: 205411

llvm-svn: 205410

Change-Id: I76d4708a26f17185efb746f4b836aa32f3f8a44f
llvm-svn: 205362

fp_t.

llvm-svn: 205344

Take advantage of the SANITIZER_COMMON_LIT_TEST_DEPS variable.

<rdar://problem/16458307>

llvm-svn: 205321

Enabling test/profile on Linux to get feedback from the buildbots.  I'm
hoping this just works...

<rdar://problem/16458307>

llvm-svn: 205319

The -flto flag relies on linker features that are not available on all
platforms.

<rdar://problem/16458307>

llvm-svn: 205318

llvm-svn: 205316

From GuanHong Liu.

Differential Revision: http://llvm-reviews.chandlerc.com/D2797

llvm-svn: 205312

llvm-svn: 205311

Based on http://llvm-reviews.chandlerc.com/D3042 by Yuri Gribov!

llvm-svn: 205308

llvm-svn: 205300

[sanitizer] one more stress test for the deadlock detector; this one stresses the slow path with a global lock

llvm-svn: 205299

llvm-svn: 205291

llvm-svn: 205290

Implement magic in compiler-rt to enable llvm-lit to be invoked on the
source tree in lib/profile.  This relies on a paired commit in the llvm
tree that exposes a new built-in parameter.

<rdar://problem/16458307>

llvm-svn: 205263

Add the test infrastructure for testing lib/profile and a single test.
This initial commit only enables the tests on Darwin, but they'll be
enabled on Linux soon after.

<rdar://problem/16458307>

llvm-svn: 205256

llvm-svn: 205192

llvm-svn: 205184

Soon there will be an option to build compiler-rt parts as shared libraries
on Linux. Extracted from http://llvm-reviews.chandlerc.com/D3042
by Yuri Gribov.

llvm-svn: 205183

llvm-svn: 205176

llvm-svn: 205175

[sanitizer] speed up the bitvector-based deadlock detector by ~15% (iterate over the currently held locks using the array, not the bitvector. Bitvector is not the best data structure to iterate over)

llvm-svn: 205168

llvm-svn: 205006

These interceptors require deep unpoisoning of return values.
While at it, we do the same for all other pw/gr interceptors to
reduce dependency on libc implementation details.

llvm-svn: 205004