diff options
| author | bors <bors@rust-lang.org> | 2022-04-10 08:57:32 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2022-04-10 08:57:32 +0000 |
| commit | 7af93292c27cd8b4a14f0f35bcb4c7e7ca9c287a (patch) | |
| tree | 1df9a46639a28741ba83c83b78d110b9ff6345a0 /compiler/rustc_llvm/llvm-wrapper/PassWrapper.cpp | |
| parent | 341883d051ebbfaa6daa456b198d557fa0272b71 (diff) | |
| parent | dec73f58d8f01c7f53ae6c50ff270af7228c0a01 (diff) | |
| download | rust-7af93292c27cd8b4a14f0f35bcb4c7e7ca9c287a.tar.gz rust-7af93292c27cd8b4a14f0f35bcb4c7e7ca9c287a.zip | |
Auto merge of #95621 - saethlin:remove-mpsc-transmute, r=RalfJung
Remove ptr-int transmute in std::sync::mpsc Since https://github.com/rust-lang/rust/pull/95340 landed, Miri with `-Zmiri-check-number-validity` produces an error on the test suites of some crates which implement concurrency tools<sup>*</sup>, because it seems like such crates tend to use `std::sync::mpsc` in their tests. This fixes the problem by storing pointer bytes in a pointer. <sup>*</sup> I have so far seen errors in the test suites of `once_cell`, `parking_lot`, and `crossbeam-utils`. (just updating the list for fun, idk) Also `threadpool`, `async-lock`, `futures-timer`, `fragile`, `scoped_threadpool`, `procfs`, `slog-async`, `scheduled-thread-pool`, `tokio-threadpool`, `mac`, `futures-cpupool`, `ntest`, `actix`, `zbus`, `jsonrpc-client-transports`, `fail`, `libp2p-gossipsub`, `parity-send-wrapper`, `async-broadcast,` `libp2p-relay`, `http-client`, `mockito`, `simple-mutex`, `surf`, `pollster`, and `pulse`. Then I turned the bot off.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/PassWrapper.cpp')
0 files changed, 0 insertions, 0 deletions