[wasm] Fix performance bug in module instantiation

Bug: chromium:1103161
Change-Id: I8b6155ec4f1033eb7024d798a08cd6f55f5f609d
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2287502Reviewed-by: Clemens Backes <clemensb@chromium.org>
Commit-Queue: Manos Koukoutos <manoskouk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#68737}

src/wasm/module-instantiate.cc

@@ -1712,7 +1712,7 @@ bool LoadElemSegmentImpl(Isolate* isolate, Handle<WasmInstanceObject> instance,
 
     // For ExternRef tables, we have to generate the WasmExternalFunction
     // eagerly. Later we cannot know if an entry is a placeholder or not.
-    if (table_object->type().is_reference_to(HeapType::kFunc)) {
+    if (table_object->type().is_reference_to(HeapType::kExtern)) {
       Handle<WasmExternalFunction> wasm_external_function =
           WasmInstanceObject::GetOrCreateWasmExternalFunction(isolate, instance,
                                                               func_index);