From 500b617b1c8ea88a2cf46f60205071da9c7569bc Mon Sep 17 00:00:00 2001 From: Ben Smith Date: Sat, 11 Nov 2017 13:36:34 -0800 Subject: Update testsuite; call_indirect has new syntax (#667) The `call_indirect` instruction now allows the type to be specified inline or via the common "type use" syntax (or both): ``` call_indirect (type $t1) ... call_indirect (param i32 f32) (result f64) ... call_indirect (type $t2) (param i32) ... ``` This means that `CallIndirectExpr` changes from storing a `Var` (the referenced func type) to a `FuncDeclaration`, which can store both a type use and a function signature. Most of the changes here are fallout from that change. The other major change is that function signature resolution and error checking now needs to iterate over a functions expr list looking for `call_indirect` instructions. I'm not sure if this is a significant overhead in parsing/validation yet, but there are plenty of ways to optimize it if it ends up in profiles. --- third_party/testsuite | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'third_party') diff --git a/third_party/testsuite b/third_party/testsuite index f470e79e..084a7b0b 160000 --- a/third_party/testsuite +++ b/third_party/testsuite @@ -1 +1 @@ -Subproject commit f470e79e25ac4bd7fbc6e714b7405c88a7aa03a8 +Subproject commit 084a7b0b0967b815f5bcd081cd3478982b904720 -- cgit v1.2.3