diff options
| author | bors <bors@rust-lang.org> | 2022-11-03 03:07:31 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2022-11-03 03:07:31 +0000 |
| commit | ce1a7e41f96be27103b6e3ba09dcefbf5bd320bd (patch) | |
| tree | ce78c1e0be62bb6366694e235c6fff845e8103cf /compiler/rustc_codegen_llvm | |
| parent | 96787c45acb623c7e39e041f44a5d98d814217e2 (diff) | |
| parent | ffccfa1eedd049c87b1ad828297ae4c4121b2e40 (diff) | |
| download | rust-ce1a7e41f96be27103b6e3ba09dcefbf5bd320bd.tar.gz rust-ce1a7e41f96be27103b6e3ba09dcefbf5bd320bd.zip | |
Auto merge of #103455 - BlackHoleFox:apple-sim-abi-consistency, r=davidtwco
Fixed consistency of Apple simulator target's ABI Currently there's a few Apple device simulator targets that are inconsistent since some set `target_abi = "sim"` (the correct thing to do) while a bunch of others don't set anything (`""`). Due to this its very hard to reliability check if some Rust code is running inside a simulator. This changes all of them to do the same thing and set `sim` as their `target_abi`. The new way to identity a simulator during compilation is as simple as `cfg(all(target_vendor="apple", target_abi = "sim"))` or even `cfg(target_abi = "sim")` being less pedantic about it. The issues with the current form (and inspiration for this) are also summarized in `@thomcc's` [Tweet](https://twitter.com/at_tcsc/status/1576685244702691328).
Diffstat (limited to 'compiler/rustc_codegen_llvm')
0 files changed, 0 insertions, 0 deletions