)]}'
{
  "commit": "11af4fc1675a4df976cb97073c16516bf8b17db2",
  "tree": "2b2ceaf29b49f4f0a29681dd747c4f2a91f4fb8b",
  "parents": [
    "a29e5e14c924426db075adb5eb00d842ccd843c4",
    "45adab87a56b12b411d3cce66b8a18942f7ac179"
  ],
  "author": {
    "name": "Jonathan Brouwer",
    "email": "jonathantbrouwer@gmail.com",
    "time": "Fri May 15 20:11:43 2026 +0200"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Fri May 15 20:11:43 2026 +0200"
  },
  "message": "Rollup merge of #156554 - guybedford:wasm-use-legacy-eh, r\u003dalexcrichton\n\nAllow user-provided `llvm_args` to override target spec arguments\n\nThis switches the order in which `-Cllvm-args` is applied between target-spec arguments and user-provided LLVM arguments.\n\nThis came up in rust-lang/rust#156061, where the target passing `-Cllvm-args\u003d-wasm-use-legacy-eh\u003dfalse` means that a user passing `-Cllvm-args\u003d-wasm-use-legacy-eh\u003dtrue` cannot override this value since the LLVM arguments support the last argument overriding the previous, and user arguments were chained first.\n\nWith this change, it is possible for Wasm targets to opt into legacy EH for compatibility with runtimes that don\u0027t yet implement the modern exnref/try_table instructions, such as Node.js 20 on V8 11.3 and older browsers. While Node.js 20 is formally EOL, many libraries will still need to support this version for a few months yet, so this would ease the transition path to modern exception handling having an opt-out.\n\nOriginally this PR added support for a dedicated `-Z` flag for switching to legacy exception handling, but fine-grained control over the arguments would be a preferable solution provided it does not conflict with other behaviours.\n\n//cc @alexcrichton\n",
  "tree_diff": []
}