summaryrefslogtreecommitdiffstats
path: root/lldb/source/Interpreter
diff options
context:
space:
mode:
authorHans Wennborg <hans@chromium.org>2020-02-05 11:03:49 +0100
committerHans Wennborg <hans@chromium.org>2020-02-06 09:02:41 +0100
commitd0104a596199a41963dbba70338d9ff3c36b185a (patch)
tree02dda439aa032f7efe51abe9c029c992ba11a72a /lldb/source/Interpreter
parentc32d809e9cae8da7d3016b6cb30e2a2a9c9e2762 (diff)
downloadbcm5719-llvm-d0104a596199a41963dbba70338d9ff3c36b185a.tar.gz
bcm5719-llvm-d0104a596199a41963dbba70338d9ff3c36b185a.zip
Make llvm::crc32() work also for input sizes larger than 32 bits.
The problem was noticed by the Chrome OS toolchain folks (crbug.com/1048445) because llvm-objcopy --add-gnu-debuglink would insert the wrong checksum when processing a binary larger than 4 GB. That use case regressed in 1e1e3ba2526 when we started using llvm::crc32() in more places. Differential revision: https://reviews.llvm.org/D74039 (cherry picked from commit 6c4a8bc0a9f6a466d90d542bef66d69550c1b041)
Diffstat (limited to 'lldb/source/Interpreter')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud