> https://github.com/kripken/emscripten/issues/2970 <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fkripken%2Femscripten%2Fissues%2F2970&sa=D&sntz=1&usg=AFQjCNFXnYTP-F1k44182kLHz4NkFRGetg> > To be honest I haven't tried source maps on huge projects. It's very possible there is a large inefficiency somewhere. Filing an issue with a testcase would help investigate.
I've seen that one before, and it's the same issue. Seems like he's posted a test case already. I wouldn't say my tests are on huge projects. It's easy to see this in the Activity Monitor when the linker goes off for minutes, and the GB just keep increasing. I think we just passed 8GB with -g4 on non-debug builds. This is the single biggest slowdown on links. It's not the optimizer. If you remove -g4, the link times are down to 1 minute or less. With it, they are more like 5-8 minutes on a quad core system with SSD. -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
