-
Notifications
You must be signed in to change notification settings - Fork 12.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wasm-ld crash when linking huge wasm binary without gc-sections #53987
Comments
@llvm/issue-subscribers-lld-wasm |
To be clear if you use Is there any way you could try narrow this down? Or at least could you attach the set of all inputs uses so its can be reproduced? |
I think I have what is likely the same failure, here's the stack obtained with a debug linker:
It seems that Edit: debug log:
|
Here's the minimal reproduction, you just need an undefined function:
Edit: I think the bug is in |
…-symbols When undefined functions exist in the final link we need to create stub functions (otherwise direct calls to those functions could not be generated). We were creating those stub when `--unresolved-symbols=ignore-all` was passed but overlooked the fact that `--warn-unresolved-symbols` essentially has the same effect (i.e. undefined function can exist in the final link). Fixes: llvm#53987
…-symbols (#78643) When undefined functions exist in the final link we need to create stub functions (otherwise direct calls to those functions could not be generated). We were creating those stub when `--unresolved-symbols=ignore-all` was passed but overlooked the fact that `--warn-unresolved-symbols` essentially has the same effect (i.e. undefined function can exist in the final link). Fixes: #53987
The complete verbose log is available at https://gist.github.com/TerrorJack/6e241c2671782e441bcd25ccaff89689.
The above verbose log and stack traces comes from the
llvmorg-14.0.0-rc1
revision onx86_64-linux
.The text was updated successfully, but these errors were encountered: