)]}'
{
  "commit": "9fe95ca30bbb79a7e01cc78407dea2c024e01c0e",
  "tree": "631a65ef919d5f898d77bccb18e07bb1d1229636",
  "parents": [
    "c2dc0c09f124e36e448a38b91176a2f9b7d34888",
    "7a8face49601c6fc3bef30ecffc3ec2e8b9ad5ae"
  ],
  "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": []
}