summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/lang/cpp
diff options
context:
space:
mode:
authorKostya Kortchinsky <kostyak@google.com>2017-05-11 21:40:45 +0000
committerKostya Kortchinsky <kostyak@google.com>2017-05-11 21:40:45 +0000
commit01a66fc928a18a0df6a53b1068a987a1a3c65029 (patch)
treec3c1bc2f82080358edf9116c8b3f52507da3b0da /lldb/packages/Python/lldbsuite/test/lang/cpp
parentc103ef89ee7abb5581ad26a3b85a31b44aa4e500 (diff)
downloadbcm5719-llvm-01a66fc928a18a0df6a53b1068a987a1a3c65029.tar.gz
bcm5719-llvm-01a66fc928a18a0df6a53b1068a987a1a3c65029.zip
[scudo] Use our own combined allocator
Summary: The reasoning behind this change is twofold: - the current combined allocator (sanitizer_allocator_combined.h) implements features that are not relevant for Scudo, making some code redundant, and some restrictions not pertinent (alignments for example). This forced us to do some weird things between the frontend and our secondary to make things work; - we have enough information to be able to know if a chunk will be serviced by the Primary or Secondary, allowing us to avoid extraneous calls to functions such as `PointerIsMine` or `CanAllocate`. As a result, the new scudo-specific combined allocator is very straightforward, and allows us to remove some now unnecessary code both in the frontend and the secondary. Unused functions have been left in as unimplemented for now. It turns out to also be a sizeable performance gain (3% faster in some Android memory_replay benchmarks, doing some more on other platforms). Reviewers: alekseyshl, kcc, dvyukov Reviewed By: alekseyshl Subscribers: llvm-commits Differential Revision: https://reviews.llvm.org/D33007 llvm-svn: 302830
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lang/cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud