diff options
| author | Sam Clegg <sbc@chromium.org> | 2018-08-22 17:27:31 +0000 |
|---|---|---|
| committer | Sam Clegg <sbc@chromium.org> | 2018-08-22 17:27:31 +0000 |
| commit | f77dc2a8d1d7bdd433d04ba2386d860f31a4f358 (patch) | |
| tree | 466d7eff31ce266626c7f368b000ed53fc6dd4d2 /clang/lib/CodeGen/CodeGenModule.cpp | |
| parent | 4fc7e6a1e95e022f9f42c6a616f21828e65f68b1 (diff) | |
| download | llvm-f77dc2a8d1d7bdd433d04ba2386d860f31a4f358.zip llvm-f77dc2a8d1d7bdd433d04ba2386d860f31a4f358.tar.gz llvm-f77dc2a8d1d7bdd433d04ba2386d860f31a4f358.tar.bz2 | |
[WebAssembly] Ensure relocation entries are ordered by offset
wasm-lld expects relocation entries to be sorted by offset. In most
cases llvm produces them in order, but the CODE section (which combines
many MCSections) is an exception because we order the functions in
Symbol order, not in section order. What is more, its not clear weather
`recordRelocation` is guaranteed to be called in offset order so this
sort of most likely needed in the general case too.
Differential Revision: https://reviews.llvm.org/D51065
llvm-svn: 340423
Diffstat (limited to 'clang/lib/CodeGen/CodeGenModule.cpp')
0 files changed, 0 insertions, 0 deletions