[GC] Add struct.set (#3430)

Mostly straightforward after struct.get.

This renames the value field in struct.get to ref. I think this makes
more sense because struct.set has both a reference to a thing, and a
value to set onto that thing. So calling the former ref seems more
consistent, giving us ref, value. This mirrors load/store for example
where we use ptr, value, and ref is playing the role of ptr here
basically.

1 files changed, 7 insertions, 6 deletions

diff --git a/src/wasm/wasm-s-parser.cpp b/src/wasm/wasm-s-parser.cpp
index 3e605429d..37592fcd5 100644
--- a/src/wasm/wasm-s-parser.cpp
+++ b/src/wasm/wasm-s-parser.cpp
@@ -2142,15 +2142,16 @@ Expression* SExpressionWasmBuilder::makeStructGet(Element& s, bool signed_) {
   auto structType = parseHeapType(*s[1]);
   auto index = getStructIndex(structType, *s[2]);
   auto type = structType.getStruct().fields[index].type;
-  auto value = parseExpression(*s[3]);
-  return Builder(wasm).makeStructGet(index, value, type, signed_);
+  auto ref = parseExpression(*s[3]);
+  return Builder(wasm).makeStructGet(index, ref, type, signed_);
 }
 
 Expression* SExpressionWasmBuilder::makeStructSet(Element& s) {
-  auto ret = allocator.alloc<StructSet>();
-  WASM_UNREACHABLE("TODO (gc): struct.set");
-  ret->finalize();
-  return ret;
+  auto structType = parseHeapType(*s[1]);
+  auto index = getStructIndex(structType, *s[2]);
+  auto ref = parseExpression(*s[3]);
+  auto value = parseExpression(*s[4]);
+  return Builder(wasm).makeStructSet(index, ref, value);
 }
 
 Expression* SExpressionWasmBuilder::makeArrayNew(Element& s, bool default_) {