)]}'
{
  "commit": "fdb324db4bcab38690e5702992b43ef729f45d7b",
  "tree": "49e7fa59e7fa89421a4dfa50b522b1e1192dd884",
  "parents": [
    "1b066cb3101dade3fe5be69218a7de41fa79599f"
  ],
  "author": {
    "name": "Derek Schuff",
    "email": "dschuff@chromium.org",
    "time": "Thu Oct 31 23:23:21 2024"
  },
  "committer": {
    "name": "Derek Schuff",
    "email": "dschuff@chromium.org",
    "time": "Thu Oct 31 23:23:21 2024"
  },
  "message": "Don\u0027t use multiple tables in wasm-split\n\nCurrently, wasm-split will create a second table rather than replacing\nthe existing one when reftypes is supported (or rather whether a\ntarget_features section is present indicating it\u0027s already used).\nBut the emscripten integration code doesn\u0027t currently support this,\nand it\u0027s not tested anywhere. The existing tests started failing when\nBinaryen stopped stripping the features section by default.\n(But some users would already be broken by this). For now, removing\nthis untested behavior is a safe default.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "f299d7a3554e73e611f962ee4b042825e28e2130",
      "old_mode": 33188,
      "old_path": "src/ir/module-splitting.cpp",
      "new_id": "ce8bab793d31bd613bb680f192729e6443a32a29",
      "new_mode": 33188,
      "new_path": "src/ir/module-splitting.cpp"
    }
  ]
}