Increase the maximum type size to 1M (#945)

In #940 there are modules in the wild running into the previous 100k
limit. This previous limit was completely arbitrarily chosen, so
increase it by 10x and see how things go. In theory 1M should still be
reasonable enough to typecheck in a modest amount of time for input
modules while still preventing excessive use of resources during
fuzzing.

Author: alexcrichton

crates/wasmparser/src/limits.rs

@@ -50,7 +50,7 @@ pub const MAX_WASM_INSTANTIATION_EXPORTS: usize = 1000;
 pub const MAX_WASM_CANONICAL_OPTIONS: usize = 10;
 pub const MAX_WASM_INSTANTIATION_ARGS: usize = 1000;
 pub const MAX_WASM_START_ARGS: usize = 1000;
-pub const MAX_WASM_TYPE_SIZE: u32 = 100_000;
+pub const MAX_WASM_TYPE_SIZE: u32 = 1_000_000;
 pub const MAX_WASM_MODULES: usize = 1_000;
 pub const MAX_WASM_COMPONENTS: usize = 1_000;
 pub const MAX_WASM_INSTANCES: usize = 1_000;

tests/local/component-model/very-nested.wast

@@ -1836,17 +1836,31 @@
       (field "f9" $t3)
     ))
 
+    ;; size(t5) == 100000
+    (type $t5 (record
+      (field "f0" $t4)
+      (field "f1" $t4)
+      (field "f2" $t4)
+      (field "f3" $t4)
+      (field "f4" $t4)
+      (field "f5" $t4)
+      (field "f6" $t4)
+      (field "f7" $t4)
+      (field "f8" $t4)
+      (field "f9" $t4)
+    ))
+
     (type $f (func
-      (param "a" $t4)
-      (param "b" $t4)
-      (param "c" $t4)
-      (param "d" $t4)
-      (param "e" $t4)
-      (param "f" $t4)
-      (param "g" $t4)
-      (param "h" $t4)
-      (param "i" $t4)
-      (param "j" $t4)
+      (param "a" $t5)
+      (param "b" $t5)
+      (param "c" $t5)
+      (param "d" $t5)
+      (param "e" $t5)
+      (param "f" $t5)
+      (param "g" $t5)
+      (param "h" $t5)
+      (param "i" $t5)
+      (param "j" $t5)
     ))
   )
   "effective type size exceeds the limit")