mirror of
https://github.com/rust-lang/rust.git
synced 2025-06-22 20:47:48 +00:00
c5efc6aada
Remove `i128` and `u128` from `improper_ctypes_definitions` Rust's 128-bit integers have historically been incompatible with C [1]. However, there have been a number of changes in Rust and LLVM that mean this is no longer the case: * Incorrect alignment of `i128` on x86 [1]: adjusting Rust's alignment proposed at https://github.com/rust-lang/compiler-team/issues/683, implemented at https://github.com/rust-lang/rust/pull/116672. * LLVM version of the above: resolved in LLVM, including ABI fix. Present in LLVM18 (our minimum supported version). * Incorrect alignment of `i128` on 64-bit PowerPC, SPARC, and MIPS [2]: Rust's data layouts adjusted at https://github.com/rust-lang/rust/pull/132422, https://github.com/rust-lang/rust/pull/132741, https://github.com/rust-lang/rust/pull/134115. * LLVM version of the above: done in LLVM 20 https://github.com/llvm/llvm-project/issues/102783. * Incorrect return convention of `i128` on Windows: adjusted to match GCC and Clang at https://github.com/rust-lang/rust/pull/134290. At https://github.com/rust-lang/lang-team/issues/255#issuecomment-2088855084, the lang team considered it acceptable to remove `i128` from `improper_ctypes_definitions` if the LLVM version is known to be compatible. Time has elapsed since then and we have dropped support for LLVM versions that do not have the x86 fixes, meaning a per-llvm-version lint should no longer be necessary. The PowerPC, SPARC, and MIPS changes only came in LLVM 20 but since Rust's datalayouts have also been updated to match, we will be using the correct alignment regardless of LLVM version. `repr(i128)` was added to this lint in https://github.com/rust-lang/rust/pull/138282, but is also removed here. Part of the decision is that `i128` should match `__int128` in C on platforms that provide it, which documentation is updated to indicate. We will not guarantee that `i128` matches `_BitInt(128)` since that can be different from `__int128`. Some platforms (usually 32-bit) do not provide `__int128`; if any ABIs are extended in the future to define it, we will need to make sure that our ABI matches. Closes: https://github.com/rust-lang/rust/issues/134288 [1]: https://github.com/rust-lang/rust/issues/54341 [2]: https://github.com/rust-lang/rust/issues/128950 |
||
|---|---|---|
| .. | ||
| early | ||
| nonstandard_style | ||
| types | ||
| async_closures.rs | ||
| async_fn_in_trait.rs | ||
| autorefs.rs | ||
| builtin.rs | ||
| context.rs | ||
| dangling.rs | ||
| default_could_be_derived.rs | ||
| deref_into_dyn_supertrait.rs | ||
| drop_forget_useless.rs | ||
| early.rs | ||
| enum_intrinsics_non_enums.rs | ||
| errors.rs | ||
| expect.rs | ||
| for_loops_over_fallibles.rs | ||
| foreign_modules.rs | ||
| if_let_rescope.rs | ||
| impl_trait_overcaptures.rs | ||
| internal.rs | ||
| invalid_from_utf8.rs | ||
| late.rs | ||
| let_underscore.rs | ||
| levels.rs | ||
| lib.rs | ||
| lints.rs | ||
| macro_expr_fragment_specifier_2024_migration.rs | ||
| map_unit_fn.rs | ||
| multiple_supertrait_upcastable.rs | ||
| non_ascii_idents.rs | ||
| non_fmt_panic.rs | ||
| non_local_def.rs | ||
| nonstandard_style.rs | ||
| noop_method_call.rs | ||
| opaque_hidden_inferred_bound.rs | ||
| pass_by_value.rs | ||
| passes.rs | ||
| precedence.rs | ||
| ptr_nulls.rs | ||
| redundant_semicolon.rs | ||
| reference_casting.rs | ||
| shadowed_into_iter.rs | ||
| static_mut_refs.rs | ||
| tests.rs | ||
| traits.rs | ||
| transmute.rs | ||
| types.rs | ||
| unit_bindings.rs | ||
| unqualified_local_imports.rs | ||
| unused.rs | ||
| utils.rs | ||