diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2022-03-02 04:30:12 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-03-02 04:30:12 +0100 |
| commit | 3ea9eebb73d07d81e7bd92ba6ec4a6da37c18ae9 (patch) | |
| tree | 9d25d306754e0262bf37f18e5f054ac733e9842a /compiler/rustc_codegen_llvm/src/context.rs | |
| parent | 1ff654af3922096737fa8642c238338305585639 (diff) | |
| parent | 75c3e9c23f07b275548998555883e34e39896587 (diff) | |
| download | rust-3ea9eebb73d07d81e7bd92ba6ec4a6da37c18ae9.tar.gz rust-3ea9eebb73d07d81e7bd92ba6ec4a6da37c18ae9.zip | |
Rollup merge of #94503 - joshtriplett:core-ffi-c, r=Amanieu
Provide C FFI types via core::ffi, not just in std Tracking issue: https://github.com/rust-lang/rust/issues/94501 The ability to interoperate with C code via FFI is not limited to crates using std; this allows using these types without std. The existing types in `std::os::raw` become type aliases for the ones in `core::ffi`. This uses type aliases rather than re-exports, to allow the std types to remain stable while the core types are unstable. This also moves the currently unstable `NonZero_` variants and `c_size_t`/`c_ssize_t`/`c_ptrdiff_t` types to `core::ffi`, while leaving them unstable. Historically, we didn't do this because these types are target-dependent. However, `core` itself is also target-dependent. `core` should not call any OS services, but it knows the target and the target's ABI.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/context.rs')
0 files changed, 0 insertions, 0 deletions