| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Differential Revision: http://reviews.llvm.org/D6825
llvm-svn: 225443
|
| |
|
|
| |
llvm-svn: 225370
|
| |
|
|
| |
llvm-svn: 225337
|
| |
|
|
| |
llvm-svn: 225336
|
| |
|
|
|
|
|
|
|
|
|
| |
This mirrors r225239 to all the rest sanitizers:
ASan, DFSan, LSan, MSan, TSan, UBSan.
Now the runtime flag type, name, default value and
description is located in the single place in the
.inc file.
llvm-svn: 225327
|
| |
|
|
| |
llvm-svn: 225323
|
| |
|
|
|
|
|
| |
Propagate -DSANITIZER_DEBUG definition to unit tests.
Make sure unit tests depend on compiler-rt headers.
llvm-svn: 225298
|
| |
|
|
| |
llvm-svn: 225293
|
| |
|
|
|
|
| |
wrong there.
llvm-svn: 225281
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Linux has 64k pages, so the old limit was only two pages. With ASLR the
initial sp might be right at the start of the second page, so the stack
will immediately grow down into the first page; and if you use all pages
of a limited stack then asan hits a kernel bug to do with how stack
guard pages are reported in /proc/self/maps:
http://lkml.iu.edu//hypermail/linux/kernel/1501.0/01025.html
We should still fix the underlying problems, but in the mean time this
patch makes the test work with 64k pages as well as it does with 4k
pages.
llvm-svn: 225261
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
Introduce a single place where we specify flag type, name, default
value, and description. This removes a large amount of boilerplate
and ensures we won't leave flags uninitialized.
Test Plan: regression test suite
Reviewers: kcc
Subscribers: llvm-commits
Differential Revision: http://reviews.llvm.org/D6851
llvm-svn: 225239
|
| |
|
|
|
|
| |
usual in most cases but will not dump coverage on error with -fno-sanitize-recover (that'll be a separate fix)
llvm-svn: 225234
|
| |
|
|
|
|
| |
instead of just one (otherwise files of > 2Gb are trunkated). Also a minor adjustment to the trace collection.
llvm-svn: 225230
|
| |
|
|
| |
llvm-svn: 225226
|
| |
|
|
|
|
|
|
|
|
|
| |
The clear_cache and enable_execute_stack tests attempt to memcpy the definition
of a function into a buffer before executing the function. The problem with
this approach is that on some targets (ARM with thumb mode compilation, MIPS
with MIPS16 codegen or uMIPS), you would use a pointer which is incorrect (it
would be off-by-one) due to the ISA selection being encoded into the address.
This ensures that the function address is retrieved correctly in all cases.
llvm-svn: 225215
|
| |
|
|
| |
llvm-svn: 225111
|
| |
|
|
| |
llvm-svn: 225110
|
| |
|
|
|
|
| |
guard page to trace array, fix the trace IDs before dumping
llvm-svn: 225108
|
| |
|
|
| |
llvm-svn: 225107
|
| |
|
|
|
|
| |
coverage
llvm-svn: 225103
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
initialization.""
Fix test failures by introducing CommonFlags::CopyFrom() to make sure
compiler doesn't insert memcpy() calls into runtime code.
Original commit message:
Protect CommonFlags singleton by adding const qualifier to
common_flags() accessor. The only ways to modify the flags are
SetCommonFlagsDefaults(), ParseCommonFlagsFromString() and
OverrideCommonFlags() functions, which are only supposed to be
called during initialization.
llvm-svn: 225088
|
| |
|
|
|
|
|
|
|
|
| |
We've got some internal users that either aren't compatible with this or
have found a bug with it. Either way, this is an isolated cleanup and so
I'm reverting it to un-block folks while we investigate. Alexey and
I will be working on fixing everything up so this can be re-committed
soon. Sorry for the noise and any inconvenience.
llvm-svn: 225079
|
| |
|
|
|
|
|
| |
During a LTO we still need to build a compiler_rt with regular object files
in the .a.
llvm-svn: 225049
|
| |
|
|
|
|
| |
fork()
llvm-svn: 225016
|
| |
|
|
|
|
| |
Useful e.g. if the user only needs coverage is bitset
llvm-svn: 225002
|
| |
|
|
|
|
|
|
|
| |
available.
(recommitting as the Clang patch is back in with the latest fix -
hopefully it sticks)
llvm-svn: 225001
|
| |
|
|
| |
llvm-svn: 224999
|
| |
|
|
| |
llvm-svn: 224988
|
| |
|
|
|
|
| |
memory range
llvm-svn: 224987
|
| |
|
|
|
|
|
|
| |
This reverts commit r221445. This change leads to false positives
reports from -fsanitize=vptr. See original commit thread for more
details.
llvm-svn: 224972
|
| |
|
|
|
|
|
|
|
|
|
| |
clang (in r224941)"
Asserting when building compiler-rt when using a gcc host compiler.
Reverting while I investigate.
This reverts commit r224942.
llvm-svn: 224969
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
Its seems to be replaced by clang_darwin.mk in the Makefile-based
build, and is only referenced in unittest scripts, which are
broken for a long time now.
Test Plan: n/a
Reviewers: bob.wilson
Subscribers: llvm-commits
Differential Revision: http://reviews.llvm.org/D6574
llvm-svn: 224946
|
| |
|
|
|
|
| |
(in r224941)
llvm-svn: 224942
|
| |
|
|
|
|
|
|
|
|
| |
LLVM_LIBDIR_SUFFIX variable to one place in the cmake file.
This is all that I had to do to get everything from compiler-rt working
for me, but there may be more work required if folks are relying on more
parts of compiler-rt. Notably, I'm mostly using it for the sanitizers.
llvm-svn: 224928
|
| |
|
|
|
|
| |
The change in r224819 started using internal_unlink in a sanitizer_common unit test. For some reason, internal_unlink is not defined in sanitizer_mac.cc, fixing that.
llvm-svn: 224910
|
| |
|
|
| |
llvm-svn: 224863
|
| |
|
|
| |
llvm-svn: 224858
|
| |
|
|
| |
llvm-svn: 224857
|
| |
|
|
|
|
| |
to make it easier to debug startup shadow mapping failures
llvm-svn: 224856
|
| |
|
|
|
|
|
| |
This increases the limit from 4M locations to 16M, reserving
64Mb virtual memory. Chrome has >5M unique coverage locations with coverage=3.
llvm-svn: 224855
|
| |
|
|
| |
llvm-svn: 224854
|
| |
|
|
|
|
|
|
| |
This is a re-commit of r224838 + r224839, previously reverted in r224850.
Test failures were likely (still can not reproduce) caused by two lit tests
using the same name for an intermediate build target.
llvm-svn: 224853
|
| |
|
|
|
|
| |
This will prevent ASan bots from hanging / timing out
llvm-svn: 224852
|
| |
|
|
|
|
| |
Flaky failures on the build bots.
llvm-svn: 224850
|
| |
|
|
| |
llvm-svn: 224841
|
| |
|
|
| |
llvm-svn: 224840
|
| |
|
|
|
|
| |
Looks like we can't use atexit() during ASan initialization on Windows.
llvm-svn: 224839
|
| |
|
|
| |
llvm-svn: 224838
|
| |
|
|
| |
llvm-svn: 224837
|
| |
|
|
|
|
|
|
|
| |
The current code leaves the first event in the trace part uninitialized
(from the previous thread). It can cause unpredictable behavior
during stack/mutexset restoration.
Initialize the first event to a fake harmless memory access.
llvm-svn: 224834
|