diff options
| author | Sam Clegg <sbc@chromium.org> | 2019-12-20 16:02:34 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-12-20 16:02:34 -0800 |
| commit | f62e171c38bea14302f9b79f7941a248ea704425 (patch) | |
| tree | 918bc227e58be2ddb8e8254d16ebb8ff7a55494d /test/binaryen.js/exception-handling.js | |
| parent | bd4cac987f19ee4f59b161a77b996ff1de46c4b9 (diff) | |
| download | binaryen-f62e171c38bea14302f9b79f7941a248ea704425.tar.gz binaryen-f62e171c38bea14302f9b79f7941a248ea704425.tar.bz2 binaryen-f62e171c38bea14302f9b79f7941a248ea704425.zip | |
Reland "Fix renaming in FixInvokeFunctionNamesWalker (#2513)" (#2542)
* Reland "Fix renaming in FixInvokeFunctionNamesWalker (#2513)"
In the previous iteration of this change we were not calling
`renameFunctions` for each of the functions we removed.
The problem manifested itself when we rename the imported function to
`emscripten_longjmp_jmpbuf` to `emscripten_longjmp`. In this case the
import of `emscripten_longjmp` already exists so we remove the import of
`emscripten_longjmp_jmpbuf` but we were not correclty calling
renameFunctions to handle the rename of all the uses.
Add an additional test case to cover the failures that we saw on the
emscripten tree.
Diffstat (limited to 'test/binaryen.js/exception-handling.js')
0 files changed, 0 insertions, 0 deletions