)]}'
{
  "commit": "4e50a445303cc01609c6286d61ad98191d2fe67a",
  "tree": "3aaf9da502d28707d30e92c03defc36cd197b34e",
  "parents": [
    "77658bcda31a704b525cce6484a9967471f42009",
    "6a950e74b7b891584fcf74354ac3d44731230a2c"
  ],
  "author": {
    "name": "Jonathan Brouwer",
    "email": "jonathantbrouwer@gmail.com",
    "time": "Fri Mar 06 18:49:47 2026 +0100"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Fri Mar 06 18:49:47 2026 +0100"
  },
  "message": "Rollup merge of #153174 - Trivo25:fix-wasm64-sync-cfg, r\u003djoboet\n\nstd: add wasm64 to sync::Once and thread_parking atomics cfg guards\n\nWhen targeting `wasm64-unknown-unknown` with atomics enabled, `std::sync::Once` and `thread_parking` fall through to the `no_threads`/`unsupported` implementations because the cfg guards only check for `wasm32`. This causes worker threads to panic with `unreachable` at runtime. The underlying futex implementations already handle both wasm32 and wasm64 correctly, only the cfg guards were missing wasm64.\n\nI tested this manually with a multithreaded wasm64 application ([o1js](https://github.com/o1-labs/o1js/)) compiled with `-Z build-std\u003dpanic_abort,std` and `-C target-feature\u003d+atomics,+bulk-memory,+mutable-globals`\n\nRelated: rust-lang/rust#83879 rust-lang/rust#77839\n\nHappy to adjust anything based on feedback\n",
  "tree_diff": []
}