-
Notifications
You must be signed in to change notification settings - Fork 3.4k
emcc out of memory #1168
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
Comments
There is a v8 arg to increase the stack size, I think. But you should probably refactor the code to avoid that huge static allocation - that's 256MB! Compile with EMCC_DEBUG=1 and look in the .ll for where it is. |
After llvm-mirror/llvm@9f86840#diff-15ffc2fb5830c3a8c3c4c354857b1631, LLVM has two behaviors: When executing llc with `-mattr=+nontrapping-fptoint`: It generates nontrapping version of instructions, those with :sat varient. When executing llc with `-mattr=-nontrapping-fptoint`: It generates trapping version of instructions, but it inserts conditional checks around them so they don't trap and clamp to the predefined value. So it seems not very possible to support this trapping test including three modes (allow, trap, and js) for wasm backend now. Related: WebAssembly/binaryen/emscripten-core#1168, emscripten-core#5863
* Disable binaryen trap test on Wasm backend After llvm-mirror/llvm@9f86840#diff-15ffc2fb5830c3a8c3c4c354857b1631, LLVM has two behaviors: When executing llc with `-mattr=+nontrapping-fptoint`: It generates nontrapping version of instructions, those with :sat varient. When executing llc with `-mattr=-nontrapping-fptoint`: It generates trapping version of instructions, but it inserts conditional checks around them so they don't trap and clamp to the predefined value. So it seems not very possible to support this trapping test including three modes (allow, trap, and js) for wasm backend now. Related: WebAssembly/binaryen/#1168, #5863
This issue has been automatically marked as stale because there has been no activity in the past 2 years. It will be closed automatically if no further activity occurs in the next 7 days. Feel free to re-open at any time if this issue is still relevant. |
I'm trying to generate javascript for Pachi, and running into an out of memory error in the emcc node process. I'm wondering if it's possible to pass v8 arguments to the process to increase max heap size.
Steps to reproduce:
Relevant output:
The text was updated successfully, but these errors were encountered: