tree 631a65ef919d5f898d77bccb18e07bb1d1229636
parent c2dc0c09f124e36e448a38b91176a2f9b7d34888
parent 7a8face49601c6fc3bef30ecffc3ec2e8b9ad5ae
author Jonathan Brouwer <jonathantbrouwer@gmail.com> 1772819387 +0100
committer GitHub <noreply@github.com> 1772819387 +0100
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsFcBAABCAAQBQJpqxO7CRC1aQ7uu5UhlAAAnZAQAFQu/5bDDskcVeEXKh/CgOAh
 udTVUP475NR+Npc49vN0KKUmvsSzbgyUshpx8GL6ImBe2GU6w6HhVHqjnUoHdln4
 NHJayPnS+xcxVYa3HVWI2mTeAMYQzumAkBQK9pAijVFjGMK1Dkna5nPEbqLUVn/e
 3hSyB89cBJOudaikOp5XiRcwZFgMtN343H+Q5POJYACNlI78A94HtEDrP/f/EkeE
 +oc8W3g5slmHy2Ax67fY4/TnfeNVzRraZ79g/1/i1t8y5XfXlX62ENEN7EAXo6ti
 5pCyNmQhZO4TmHm3hzvZsxGCXd2zIRCjzq6dhF6HzWbeUpTiFAt0lt0Bs5Jlo5V+
 cr7LHxFe3Ue4nnFfgMFNkxhe3nvWG/pIyIdpz9SXKkpuNJdnN/tGmzpv7pms1PBM
 MNmMpzhM/MkIbjdhtnwmcRgQfVwO3zuVYSjg5174EPdsOmLSQ9yaLJpco5BLzje4
 eDTdJBa41jIN3fa0sTRkV5fm65eVqWak8a82dv8Rc/oFzxJl2K7srv6gJJFtSkbG
 xZfpii6Uk/LL+htSJCTIKoJyr8ytJDCAntZlOrdq2BOBWIZoxE9CG8+D9Oeg+61y
 m8W0ejeGewGBjMLuA3hCZOcuVQ4wY7/Fllq3MvKT+HPNG9AbUWZnZfPMPX2xISz9
 o7+GwGV278QYZIBtP/J1
 =hYYG
 -----END PGP SIGNATURE-----
 

Rollup merge of #153174 - Trivo25:fix-wasm64-sync-cfg, r=joboet

std: add wasm64 to sync::Once and thread_parking atomics cfg guards

When 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.

I tested this manually with a multithreaded wasm64 application ([o1js](https://github.com/o1-labs/o1js/)) compiled with `-Z build-std=panic_abort,std` and `-C target-feature=+atomics,+bulk-memory,+mutable-globals`

Related: rust-lang/rust#83879 rust-lang/rust#77839

Happy to adjust anything based on feedback