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

Figure out why compiling with debug symbols is so slow #216

Closed
kripken opened this Issue Feb 4, 2012 · 1 comment

Comments

Projects
None yet
1 participant
@kripken
Owner

kripken commented Feb 4, 2012

If the source code was compiled with -g, emscripten parses the debug into and adds it to the generated code. For some reason, the preparsing of the debug info spikes memory in node (not in spidermonkey), and memory usage remains high (in both node and spidermonkey) compared to the same code without debug info.

Compiling without debug info is now very fast in emscripten (faster than compiling the source to bitcode), would be nice if debug info builds were fast too.

@kripken

This comment has been minimized.

Show comment
Hide comment
@kripken

kripken Jul 12, 2012

Owner

The reason is a combination of LLVM slowness on large amounts of debug info, and handling of huge strings in emscripten's debug info handling. Not sure we can do much but wait for the C++ backend to tix the latter.

Owner

kripken commented Jul 12, 2012

The reason is a combination of LLVM slowness on large amounts of debug info, and handling of huge strings in emscripten's debug info handling. Not sure we can do much but wait for the C++ backend to tix the latter.

@kripken kripken closed this Jul 12, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment