summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2018-09-06Merging r341442:llvm_70-amp-20181130release_70-e8af9b4c407-amp-20181130Hans Wennborg
------------------------------------------------------------------------ r341442 | bcain | 2018-09-05 04:15:54 +0200 (Wed, 05 Sep 2018) | 8 lines Add glibc_prereq to platform limits mmsghdr sendmmsg requires glibc >= 2.14. Fixes PR38589. Review: https://reviews.llvm.org/D51538 ------------------------------------------------------------------------ git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/branches/release_70@341524 91177308-0d34-0410-b5e6-96231b3b80d8
2018-08-28Merging r340758 and r340769:Hans Wennborg
------------------------------------------------------------------------ r340758 | vitalybuka | 2018-08-27 19:26:28 +0200 (Mon, 27 Aug 2018) | 5 lines Revert "[lsan] Do not check for leaks in the forked process" Users need leak reports in forks. This reverts commit r334036. ------------------------------------------------------------------------ ------------------------------------------------------------------------ r340769 | vitalybuka | 2018-08-27 21:15:05 +0200 (Mon, 27 Aug 2018) | 3 lines [lsan] Check that leak sanitizer works in the forked process Regression test for PR38698 ------------------------------------------------------------------------ git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/branches/release_70@340801 91177308-0d34-0410-b5e6-96231b3b80d8
2018-08-09Merging r339303:Hans Wennborg
------------------------------------------------------------------------ r339303 | george.karpenkov | 2018-08-09 02:41:22 +0200 (Thu, 09 Aug 2018) | 11 lines [libFuzzer] Increase the iteration limit in shrink.test After https://reviews.llvm.org/D48800, shrink.test started failing on x86_64h architecture. Looking into this, the optimization pass is too eager to unroll the loop on x86_64h, possibly leading to worse coverage data. Alternative solutions include not unrolling the loop when fuzzing, or disabling this test on that architecture. Differential Revision: https://reviews.llvm.org/D50484 ------------------------------------------------------------------------ git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/branches/release_70@339315 91177308-0d34-0410-b5e6-96231b3b80d8
2018-08-02Merging r338606:Hans Wennborg
------------------------------------------------------------------------ r338606 | kcc | 2018-08-01 20:29:51 +0200 (Wed, 01 Aug 2018) | 11 lines Fix sizeof(struct pthread) in glibc 2.14. Summary: Fixes: https://github.com/google/sanitizers/issues/966 Reviewers: kcc Reviewed By: kcc Subscribers: kubamracek Differential Revision: https://reviews.llvm.org/D50131 ------------------------------------------------------------------------ git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/branches/release_70@338691 91177308-0d34-0410-b5e6-96231b3b80d8
2018-08-02Merging r338577:Hans Wennborg
------------------------------------------------------------------------ r338577 | filcab | 2018-08-01 17:30:14 +0200 (Wed, 01 Aug 2018) | 1 line Add missing condition ------------------------------------------------------------------------ git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/branches/release_70@338690 91177308-0d34-0410-b5e6-96231b3b80d8
2018-08-01Creating release_70 branch off revision 338536Hans Wennborg
git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/branches/release_70@338541 91177308-0d34-0410-b5e6-96231b3b80d8
2018-08-01Test: Enable exceptions for test that needs itFilipe Cabecinhas
git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@338535 91177308-0d34-0410-b5e6-96231b3b80d8
2018-08-01[gcov] Add test which uses forkMarco Castelluccio
Test for https://bugs.llvm.org/show_bug.cgi?id=38180. git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@338500 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-31[compiler-rt] Add a routine to specify the mode used when creating profile dirs.Matt Davis
Summary: This patch introduces `llvm_profile_set_dir_mode` and `llvm_profile_get_dir_mode` to the compiler-rt profile API. Originally, profile data was placed into a directory that was created with a hard-coded mode value of 0755 (for non-win32 builds). In certain cases, it can be helpful to create directories with a different mode other than 0755. This patch introduces set/get routines to allow users to specify a desired mode. The default remains at 0755. Reviewers: void, probinson Reviewed By: probinson Subscribers: probinson, dberris, cfe-commits Differential Revision: https://reviews.llvm.org/D49953 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@338456 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-31[gcov] Add tests using switch, one with break clauses and one with fallthroughMarco Castelluccio
git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@338453 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-31[XRay][compiler-rt] Update test to use similar structureDean Michael Berris
This is a follow-up to D50037. git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@338349 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-31[XRay][compiler-rt] Profiling Mode: Include file header in buffersDean Michael Berris
Summary: This change provides access to the file header even in the in-memory buffer processing. This allows in-memory processing of the buffers to also check the version, and the format, of the profile data. Reviewers: eizan, kpw Reviewed By: eizan Subscribers: llvm-commits Differential Revision: https://reviews.llvm.org/D50037 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@338347 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-31Pacify sanitizer lint script that still does not run on WindowsReid Kleckner
git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@338334 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-30[asan/win] Use SRW locks to fix a race in BlockingMutexReid Kleckner
Summary: Before my change, BlockingMutex used Windows critial sections. Critical sections can only be initialized by calling InitializeCriticalSection, dynamically. The primary sanitizer allocator expects to be able to reinterpret zero initialized memory as a BlockingMutex and immediately lock it. RegionInfo contains a mutex, and it placement new is never called for it. These objects are accessed via: RegionInfo *GetRegionInfo(uptr class_id) const { DCHECK_LT(class_id, kNumClasses); RegionInfo *regions = reinterpret_cast<RegionInfo *>(SpaceEnd()); return &regions[class_id]; } The memory comes from the OS without any other initialization. For various reasons described in the comments, BlockingMutex::Lock would check if the object appeared to be zero-initialized, and it would lazily call the LinkerInitialized constructor to initialize the critical section. This pattern is obviously racy, and the code had a bunch of FIXMEs about it. The best fix here is to use slim reader writer locks, which can start out zero-initialized. They are available starting in Windows Vista. I think it's safe to go ahead and use them today. Reviewers: kcc, vitalybuka Subscribers: kubamracek, llvm-commits Differential Revision: https://reviews.llvm.org/D49893 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@338331 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-30[NFC] Rename test/ubsan/TestCases/{ImplicitCast => ImplicitConversion}Roman Lebedev
Just to be consistent with the rest. I should have done that in the commit itself, but the filepaths is one thing i forgot to verify :S git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@338307 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-30[compiler-rt] integer-truncation-blacklist.c: XFAIL on android/iosRoman Lebedev
The Builder sanitizer-x86_64-linux-android is failing starting with rL338287 / D48959. It runs the tests via android_compile.py, so i'm not sure this is actually *this* issue: https://code.google.com/p/address-sanitizer/issues/detail?id=316 but this seems oddly similar to the other XFAIL'ed cases... Right now that seems to be the only failing builder, so i *think* it makes sense to try to just blacklist it for now. git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@338296 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-30[compiler-rt][ubsan] Implicit Conversion Sanitizer - integer truncation - ↵Roman Lebedev
compiler-rt part Summary: This is a compiler-rt part. The clang part is D48958. See [[ https://bugs.llvm.org/show_bug.cgi?id=21530 | PR21530 ]], https://github.com/google/sanitizers/issues/940. Reviewers: #sanitizers, samsonov, vsk, rsmith, pcc, eugenis, kcc, filcab Reviewed By: #sanitizers, vsk, filcab Subscribers: llvm-commits, eugenis, filcab, kubamracek, dberris, #sanitizers, regehr Tags: #sanitizers Differential Revision: https://reviews.llvm.org/D48959 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@338287 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-30[cmake] [ARM] Exclude any VFP builtins if VFP is not supportedAzharuddin Mohammed
Summary: rL325492 disables FPU features when using soft floating point (-mfloat-abi=soft), which is used internally when building for arm. This causes errors with builtins that utililize VFP instructions. With this change we check if VFP is enabled (by checking if the preprocessor macro __VFP_FP__ is defined), and exclude such builtins if it is not enabled. Reviewers: rengolin, samsonov, compnerd, smeenai, javed.absar, peter.smith Reviewed By: peter.smith Subscribers: delcypher, peter.smith, mgorny, kristof.beyls, chrib, llvm-commits Differential Revision: https://reviews.llvm.org/D47217 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@338284 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-30[XRay][compiler-rt] FDR Mode: Use mmap instead of internal allocatorDean Michael Berris
Summary: This change moves FDR mode to use `internal_mmap(...)` from sanitizer_common instead of the internal allocator interface. We're doing this to sidestep the alignment issues we encounter with the `InternalAlloc(...)` functions returning pointers that have some magic bytes at the beginning. XRay copies bytes into the buffer memory, and does not require the magic bytes tracking the other sanitizers use when allocating/deallocating buffers. Reviewers: kpw, eizan Subscribers: llvm-commits Differential Revision: https://reviews.llvm.org/D49972 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@338228 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-30[asan] Fix typoFangrui Song
git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@338225 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-28Fix Asan-i386-calls-Test AddressSanitizer.ShadowGapTest on FreeBSDFangrui Song
0x22000000 happens to be on the left of a heap allocation and the error message is different (heap-buffer-overflow). FreeBSD NetBSD have larger SHADOW_OFFSET (0x40000000) but let's try not using #ifdef here. git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@338208 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-26[test] Use printf instead of C++ iostream, NFC.Jonas Hahnfeld
This test fails with libc++ when built with MemorySanitizer. This is because we link to an uninstrumented version of the library so msan detects a nested error when calling std::cout << "...". This can be easily avoided by using good old printf. Differential Revision: https://reviews.llvm.org/D49867 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@338053 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-26[tsan] Fix gcc pedantic warningDmitry Vyukov
Fix gcc (7.2.0) pedantic warning warning: extra ‘;’ [-Wpedantic] Author: jasonl220 (Jason Lovett) Review: https://reviews.llvm.org/D49817 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@338023 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-26[sanitizer] Include signal.h instead of sys/signal.hFangrui Song
git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@338004 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-25[libFuzzer] Disable handle-unstable.test for ARM and delete duplicated test ↵Max Moroz
file. Summary: This change should fix the failures mentioned in https://reviews.llvm.org/D49684#1175245 Reviewers: kevinwkt, morehouse, metzman Reviewed By: kevinwkt, morehouse Subscribers: kristof.beyls, delcypher, chrib, #sanitizers, llvm-commits, kcc Differential Revision: https://reviews.llvm.org/D49810 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@337949 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-25[XRay tests] Don't filter test-critical callsJeremy Morse
By default, xray filters events that takes less than 5uS from its log. In this existing test, should printf complete very quickly this will lead to test-critical function calls being filtered (i.e. print_parent_tid). Given that we're not testing the filtering feature, disable it for this test. git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@337929 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-25[Asan][Msan] Unit tests Disable some tests for FreeBSDDavid Carlier
Reviewers: krytarowski Reviewed By: krytarowski Differential Revision: https://reviews.llvm.org/D49784 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@337913 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-25[profile] Support profiling runtime on FuchsiaPetr Hosek
This ports the profiling runtime on Fuchsia and enables the instrumentation. Unlike on other platforms, Fuchsia doesn't use files to dump the instrumentation data since on Fuchsia, filesystem may not be accessible to the instrumented process. We instead use the data sink to pass the profiling data to the system the same sanitizer runtimes do. Differential Revision: https://reviews.llvm.org/D47208 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@337881 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-24[sanitizer] Update symbolizer test.Matt Morehouse
git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@337872 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-24[libFuzzer] Handle unstable edges by disregarding unstable edgesMax Moroz
Summary: Added a new mode within flag -handle_unstable for new unstable handling algorithm that does the following: When an edge is shown as unstable, copy to UnstableCounters the value 0. During ApplyUnstableCounters we copy back the value 0 to ModuleInline8bitCounters if the edge was unstable. This way we would be ignoring completely features that were collected through non-determinism. Unstable hits would be counted as if it never hit. Reviewers: metzman, Dor1s, kcc, morehouse Reviewed By: metzman, morehouse Subscribers: delcypher, llvm-commits, #sanitizers Differential Revision: https://reviews.llvm.org/D49684 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@337853 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-24[tsan] Fix crash in objc_sync_enter/objc_sync_exit when using an Obj-C ↵Kuba Mracek
tagged pointer Objective-C tagged pointers (either bottom-most or top-most bit is 1) are valid Obj-C objects but are not valid pointers. Make sure we don't crash on them when used in objc_sync_enter/objc_sync_exit. Instead, let's synchronize on a global object. Differential Revision: https://reviews.llvm.org/D49707 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@337837 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-24[profile] Fix finding the first and last directory separators on Windows.Igor Kudrin
Until now, our code preferred backslashes to slashes, whereas Windows allows using both types of directory separators in one path string. Differential Revision: https://reviews.llvm.org/D49664 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@337826 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-24[profile] Fix a possible memory leak in parseFilenamePattern().Igor Kudrin
Differential Revision: https://reviews.llvm.org/D49666 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@337823 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-24[sanitizer][fuzzer] Temporarily transition to ZX_TIME_INFINITE_OLDPetr Hosek
This is a preparation for breaking change when all Zircon calls that take time as an argument will start using signed valued. We will transition back to ZX_TIME_INFITINE after all the changes to these symbols are done and become part of the Fuchsia SDK. Differential Revision: https://reviews.llvm.org/D49694 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@337802 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-24[sanitizer] Transition from _zx_vmar_... to _zx_vmar_..._old callsPetr Hosek
This is a preparation for breaking changes to _zx_vmar_... calls. We will transition back to _zx_vmar_... after all the changes to these symbols are done and become part of the Fuchsia SDK. Differential Revision: https://reviews.llvm.org/D49697 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@337801 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-24Revert "[Fuzzer] Update path to libc++ headers"Petr Hosek
This reverts commit r337775 since r337727 has been reverted in r337782. git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@337784 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-23[Fuzzer] Update path to libc++ headersPetr Hosek
The path to headers which are installed into libc++ build directory has changed in r337727 which broke the libFuzzer build. Differential Revision: https://reviews.llvm.org/D49705 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@337775 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-23Reapply "[XRay] Remove scheduling dependency in fork_basic_logging.cc"Matthew Voss
Summary: Continuation of https://reviews.llvm.org/D49501 Second part of the test has an scheduling order when there shouldn't be. Reviewers: dberris, ormris Reviewed By: dberris, ormris Subscribers: TWeaver Differential Revision: https://reviews.llvm.org/D49559 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@337745 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-23Landed XRay patch (D49559) in incorrect directory. Reverting changes. Henry Zhu
git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@337733 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-23[XRay] Remove scheduling dependency in fork_basic_logging.ccHenry Zhu
Summary: Continuation of https://reviews.llvm.org/D49501 Second part of the test has an scheduling order when there shouldn't be. Reviewers: dberris, ormris Reviewed By: dberris, ormris Subscribers: TWeaver Differential Revision: https://reviews.llvm.org/D49559 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@337724 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-23[libFuzzer] Handle unstable edges by using minimum hit countsMax Moroz
Summary: Created unstable_handle flag that takes 1 or 2, depending on the handling type. Modified RunOne to accommodate the following heuristic: Use the first CollectFeatures to count how many features there are. If no new features, CollectFeatures like before. If there is new feature, we run CB 2 more times, Check which edges are unstable per input and we store the least amount of hit counts for each edge. Apply these hit counts back to inline8bitcounters so that CollectFeatures can work as intended. Modified UnstableCounters to 8int_t and created a bitset UnstableSet to tell which edges are unstable. Patch by Kyungtak Woo (@kevinwkt). Reviewers: Dor1s, metzman, morehouse Reviewed By: Dor1s, morehouse Subscribers: delcypher, #sanitizers, llvm-commits, kcc Differential Revision: https://reviews.llvm.org/D49525 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@337696 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-20Change the cap on the amount of padding for each vtable to 32-byte ↵Peter Collingbourne
(previously it was 128-byte) We tested different cap values with a recent commit of Chromium. Our results show that the 32-byte cap yields the smallest binary and all the caps yield similar performance. Based on the results, we propose to change the cap value to 32-byte. Patch by Zhaomo Yang! Differential Revision: https://reviews.llvm.org/D49405 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@337622 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-20Mark REAL(swapcontext) with indirect_return attribute on x86H.J. Lu
When shadow stack from Intel CET is enabled, the first instruction of all indirect branch targets must be a special instruction, ENDBR. lib/asan/asan_interceptors.cc has ... int res = REAL(swapcontext)(oucp, ucp); ... REAL(swapcontext) is a function pointer to swapcontext in libc. Since swapcontext may return via indirect branch on x86 when shadow stack is enabled, as in this case, int res = REAL(swapcontext)(oucp, ucp); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This function may be returned via an indirect branch. Here compiler must insert ENDBR after call, like call *bar(%rip) endbr64 I opened an LLVM bug: https://bugs.llvm.org/show_bug.cgi?id=38207 to add the indirect_return attribute so that it can be used to inform compiler to insert ENDBR after REAL(swapcontext) call. We mark REAL(swapcontext) with the indirect_return attribute if it is available. This fixed: https://bugs.llvm.org/show_bug.cgi?id=38249 Reviewed By: eugenis Differential Revision: https://reviews.llvm.org/D49608 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@337603 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-20On Darwin switch from the `VM_MEMORY_ANALYSIS_TOOL` VM tag toDan Liew
`VM_MEMORY_SANITIZER`. It turns out that `VM_MEMORY_ANALYSIS_TOOL` is already reserved for use by other tools so switch to a tag reserved for use by the Sanitizers. rdar://problem/41969783 Differential Revision: https://reviews.llvm.org/D49603 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@337579 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-20[scudo] Simplify internal names (NFC)Kostya Kortchinsky
Summary: There is currently too much redundancy in the class/variable/* names in Scudo: - we are in the namespace `__scudo`, so there is no point in having something named `ScudoX` to end up with a final name of `__scudo::ScudoX`; - there are a lot of types/* that have `Allocator` in the name, given that Scudo is an allocator I figure this doubles up as well. So change a bunch of the Scudo names to make them shorter, less redundant, and overall simpler. They should still be pretty self explaining (or at least it looks so to me). The TSD part will be done in another CL (eg `__scudo::ScudoTSD`). Reviewers: alekseyshl, eugenis Reviewed By: alekseyshl Subscribers: delcypher, #sanitizers, llvm-commits Differential Revision: https://reviews.llvm.org/D49505 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@337557 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-20esan: fix shadow setupDmitry Vyukov
r337531 changed return type of MmapFixedNoReserve, but esan wasn't updated. As the result esan shadow setup always fails. We probably need to make MmapFixedNoAccess signature consistent with MmapFixedNoReserve. But this is just to unbreak tests. git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@337550 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-20[Xray] fix c99 warning build about flexible array semanticsDavid Carlier
Reviewers: dberris Reviewed By: dberris Differential Revision: https://reviews.llvm.org/D49590 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@337536 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-20sanitizers: consistently check result of MmapFixedNoReserveDmitry Vyukov
MmapFixedNoReserve does not terminate process on failure. Failure to check its result and die will always lead to harder to debug crashes later in execution. This was observed in Go processes due to some address space conflicts. Consistently check result of MmapFixedNoReserve. While we are here also add warn_unused_result attribute to prevent such bugs in future and change return type to bool as that's what all callers want. Reviewed in https://reviews.llvm.org/D49367 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@337531 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-20[libFuzzer] Use separate test directory for each configJoel E. Denny
Previously, check-all failed many tests for me. It was running the X86_64DefaultLinuxConfig, X86_64LibcxxLinuxConfig, and X86_64StaticLibcxxLinuxConfig configs out of llvm-build/projects/compiler-rt/test/fuzzer. Now, it runs them out of separate subdirectories there, and most tests pass. Reviewed By: morehouse, george.karpenkov Differential Revision: https://reviews.llvm.org/D49249 git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@337521 91177308-0d34-0410-b5e6-96231b3b80d8
2018-07-19[libFuzzer] when -print_coverage=1 is given, print more stats (the number of ↵Kostya Serebryany
seeds that hit every given function) git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@337501 91177308-0d34-0410-b5e6-96231b3b80d8
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-25 02:29:15 +0000