wasm2js: run full optimizations during the pipeline (#2071)

We flatten for the i64 lowering etc. passes, and it is worth optimizing afterwards, to clean up stuff they created. That is run if the user ran wasm2js with an optimization level (like wasm2js -O3).

Split the test files to check both optimized and unoptimized code.

1 files changed, 5 insertions, 5 deletions

diff --git a/test/wasm2js/func_ptrs.2asm.js b/test/wasm2js/func_ptrs.2asm.js
index 708879e51..5ad0aff27 100644
--- a/test/wasm2js/func_ptrs.2asm.js
+++ b/test/wasm2js/func_ptrs.2asm.js
@@ -29,12 +29,12 @@ function asmFunc(global, env, buffer) {
  
  function $4($0) {
   $0 = $0 | 0;
-  return $0 + 1 | 0;
+  return $0 + 1 | 0 | 0;
  }
  
  function $5(a) {
   a = a | 0;
-  return a - 2 | 0;
+  return a - 2 | 0 | 0;
  }
  
  function $6($0) {
@@ -102,12 +102,12 @@ function asmFunc(global, env, buffer) {
  
  function $5(i) {
   i = i | 0;
-  return FUNCTION_TABLE[i]() | 0;
+  return FUNCTION_TABLE[i]() | 0 | 0;
  }
  
  function $6(i) {
   i = i | 0;
-  return FUNCTION_TABLE[i]() | 0;
+  return FUNCTION_TABLE[i]() | 0 | 0;
  }
  
  var FUNCTION_TABLE = [t1, t2, t3, u1, u2, t1, t3];
@@ -154,7 +154,7 @@ function asmFunc(global, env, buffer) {
  
  function $2(i) {
   i = i | 0;
-  return FUNCTION_TABLE[i]() | 0;
+  return FUNCTION_TABLE[i]() | 0 | 0;
  }
  
  var FUNCTION_TABLE = [t1, t2];