diff options
| author | Sam Clegg <sbc@chromium.org> | 2019-12-17 10:18:31 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-12-17 10:18:31 -0800 |
| commit | f0a2e2c75c7bb3008f10b6edbb8dc4cfd27b7d28 (patch) | |
| tree | a2528d33829d4ffde68bb7b976ebeee53ad7609d /src/binaryen-c.cpp | |
| parent | fad92eaf2092efddf84da455d4af8431d5f87592 (diff) | |
| download | binaryen-f0a2e2c75c7bb3008f10b6edbb8dc4cfd27b7d28.tar.gz binaryen-f0a2e2c75c7bb3008f10b6edbb8dc4cfd27b7d28.tar.bz2 binaryen-f0a2e2c75c7bb3008f10b6edbb8dc4cfd27b7d28.zip | |
Fix renaming in FixInvokeFunctionNamesWalker (#2513)
This fixes https://github.com/emscripten-core/emscripten/issues/9950.
The issue only shows up when debug names are not present so most of
the changes in CL come from disabling debug names in the lld tests.
We want to make sure that wasm-emscripten-finalize runs fine without
debug names so I think it makes most sense to test in this mode.
The actual bugfix is in wasm-emscripten.cpp as part of the
FixInvokeFunctionNamesWalker. The problem was the name of the function
rather than is import name was being added to importRenames. This means
that when debug names were present (and the two names were the same)
we didn't see the bug.
Diffstat (limited to 'src/binaryen-c.cpp')
0 files changed, 0 insertions, 0 deletions