From 9b7c27056eccfa8f95dc2c61fe969ab6f353757a Mon Sep 17 00:00:00 2001 From: Alon Zakai Date: Sun, 16 Mar 2014 12:01:48 -0700 Subject: comment on outlining downsides --- src/settings.js | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'src/settings.js') diff --git a/src/settings.js b/src/settings.js index 6e644a54..8e0d9e2d 100644 --- a/src/settings.js +++ b/src/settings.js @@ -165,6 +165,11 @@ var OUTLINING_LIMIT = 0; // A function size above which we try to automatically // throughput. It is hard to say what values to start testing // with, but something around 20,000 to 100,000 might make sense. // (The unit size is number of AST nodes.) + // Outlining decreases maximum function size, but does so at the + // cost of increasing overall code size as well as performance + // (outlining itself makes code less optimized, and requires + // emscripten to disable some passes that are incompatible with + // it). var AGGRESSIVE_VARIABLE_ELIMINATION = 0; // Run aggressiveVariableElimination in js-optimizer.js -- cgit v1.2.3-18-g5258