summaryrefslogtreecommitdiffstats
path: root/clang/lib/Frontend/MultiplexConsumer.cpp
diff options
context:
space:
mode:
authorHans Wennborg <hans@hanshq.net>2018-08-07 07:43:13 +0000
committerHans Wennborg <hans@hanshq.net>2018-08-07 07:43:13 +0000
commit57c21c9592ce63af90556aeb0c37805f20c2d19a (patch)
tree71dc6838c01dee2a5fba506a5ca207fd5b9b8614 /clang/lib/Frontend/MultiplexConsumer.cpp
parent54bbd10d8d61302dfa6c04daf1eee68d3a7e5bd0 (diff)
downloadbcm5719-llvm-57c21c9592ce63af90556aeb0c37805f20c2d19a.tar.gz
bcm5719-llvm-57c21c9592ce63af90556aeb0c37805f20c2d19a.zip
Merging r338949:
------------------------------------------------------------------------ r338949 | lemo | 2018-08-04 04:15:26 +0200 (Sat, 04 Aug 2018) | 27 lines Fix a bug in VMRange I noticed a suspicious failure: [ RUN ] VMRange.CollectionContains llvm/src/tools/lldb/unittests/Utility/VMRangeTest.cpp:146: Failure Value of: VMRange::ContainsRange(collection, VMRange(0x100, 0x104)) Actual: false Expected: true Looking at the code, it is a very real bug: class RangeInRangeUnaryPredicate { public: RangeInRangeUnaryPredicate(VMRange range) : _range(range) {} // note that _range binds to a temporary! bool operator()(const VMRange &range) const { return range.Contains(_range); } const VMRange &_range; }; This change fixes the bug. Differential Revision: https://reviews.llvm.org/D50290 ------------------------------------------------------------------------ llvm-svn: 339107
Diffstat (limited to 'clang/lib/Frontend/MultiplexConsumer.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud