Wasm compilation is extremely slow for large functions |
|||
Issue descriptionLarge wasm function (size over a MB) is extremely slow to compile. This was discovered while investigating the following bug: https://bugs.chromium.org/p/chromium/issues/detail?id=769607 With large wasm functions (up to 7MB) under discussion, this needs to be addressed.
,
Nov 1
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 1
Ben, is this bug still relevant? Guessing no, given Liftoff (you mention baseline compile in #c6 in issue 769607 )?
,
Nov 1
I can report that in Chrome 69.0.3497.100 (64 linux) the problem exists ( issue 769607 ) as in a year before. Chrome is very very slow to compile this js code. Because 769607 was closed as WontFix, I wrote a short program to split big functions into smaller one. This workaround solved my problem. But, as for me it's not acceptable to close this bug, because problem is actually exists. |
|||
►
Sign in to add a comment |
|||
Comment 1 by adamk@chromium.org
, Oct 31 2017