arsnyder16

This surprised me but there are some extremely long function names. Some in the hundreds of thousands  If i strip the debug information out and let the optimizer work...

Great! Thanks here is my -Os output ```[PassRunner] running passes [PassRunner] running pass: duplicate-function-elimination... 14.2522 seconds. [PassRunner] running pass: memory-packing... 0.423822 seconds. [PassRunner] running pass: once-reduction... 0.322653 seconds. [PassRunner] running...

Thanks for the pointers, pulled the repo and built, going to dig in a little and see what i find

@kripken I am close with some improvements specifically for dae-optimizing . Just so I can get an accurate before and after what is the toolkit used for the prebuilt binaries...

Thanks this is helpful, there is a difference between the two, thats why i asked since i noticed my times were off once i started building myself For example on...

@kripken With the release of firefox 100 wasm exceptions seems to now be supported by all major browsers by default. So i was switching my build process to use wasm...

@kripken Thanks thats a good head start know somewhere rse might be the common bottleneck, based on initial profiling nothing was glaring. I am going to continue to investigate No...

I have it isolated to a single function that spends about 4 minutes in `RedundantSetElimination::flowValues`. Going to try and isolate it into a simple repro

@kripken Here is an example that replicas the problem, not to the same extreme but the issue is still show. Basically a function with a large map that is use...

@kripken Few more observation, instead of using an initializer list , switching to just emplace and the overhead basically goes away. Makes me wonder why the emitted code of the...