aboutsummaryrefslogtreecommitdiff
path: root/llvm/tools/llvm-cov/CodeCoverage.cpp
diff options
context:
space:
mode:
authorSam Clegg <sbc@chromium.org>2021-05-11 11:08:14 -0700
committerSam Clegg <sbc@chromium.org>2021-05-11 12:05:14 -0700
commitb49a798e71f922a68628ad9e31ca12fdb864c2f5 (patch)
treebc3e257796361210eb3d8683a243745896456183 /llvm/tools/llvm-cov/CodeCoverage.cpp
parent9558b602b22cb7d681757c5f56d941e39a9d9d19 (diff)
downloadllvm-b49a798e71f922a68628ad9e31ca12fdb864c2f5.zip
llvm-b49a798e71f922a68628ad9e31ca12fdb864c2f5.tar.gz
llvm-b49a798e71f922a68628ad9e31ca12fdb864c2f5.tar.bz2
[lld][WebAssembly] Remove relocation target verification
We have this extra step in wasm-ld that doesn't exist in other lld backend which verifies the existing contents of the relocation targets. This was originally intended as an extra form of double checking and an aid to compiler developers. However it has always been somewhat controversial and there have been suggestions in the past the we simply remove it. My motivation for removing it now is that its causing me a headache when trying to fix an issue with negative addends. In the case of negative addends that final result can be wrapped/negative but this checking code would require significant modification to be able to deal with that case. For example with some test cases I'm looking at I'm seeing error like this: ``` wasm-ld: warning: /usr/local/google/home/sbc/dev/wasm/llvm-build/tools/lld/test/wasm/Output/merge-string.s.tmp.o:(.rodata_relocs): unexpected existing value for R_WASM_MEMORY_ADDR_I32: existing=FFFFFFFA expected=FFFFFFFFFFFFFFFA ``` Rather than try to refactor `calcExpectedValue` to somehow return two different types of results (32 and 64-bit) depending on the relocation type, I think we can just remove this code. Differential Revision: https://reviews.llvm.org/D102265
Diffstat (limited to 'llvm/tools/llvm-cov/CodeCoverage.cpp')
0 files changed, 0 insertions, 0 deletions