c8b76bcf58
On some architectures, vector types may have a different ABI depending on whether the relevant target features are enabled. (The ABI when the feature is disabled is often not specified, but LLVM implements some de-facto ABI.) As discussed in rust-lang/lang-team#235, this turns out to very easily lead to unsound code. This commit makes it a post-monomorphization future-incompat warning to declare or call functions using those vector types in a context in which the corresponding target features are disabled, if using an ABI for which the difference is relevant. This ensures that these functions are always called with a consistent ABI. See the [nomination comment](https://github.com/rust-lang/rust/pull/127731#issuecomment-2288558187) for more discussion. Part of #116558
17 lines
751 B
Plaintext
17 lines
751 B
Plaintext
error[E0391]: cycle detected when computing layout of `Wrapper<()>`
|
|
|
|
|
= note: ...which requires computing layout of `<() as Trait>::Assoc`...
|
|
= note: ...which again requires computing layout of `Wrapper<()>`, completing the cycle
|
|
= note: cycle used when computing layout of `core::option::Option<Wrapper<()>>`
|
|
= note: see https://rustc-dev-guide.rust-lang.org/overview.html#queries and https://rustc-dev-guide.rust-lang.org/query.html for more information
|
|
|
|
note: the above error was encountered while instantiating `fn abi::<()>`
|
|
--> $DIR/post-mono-layout-cycle.rs:19:5
|
|
|
|
|
LL | abi::<T>(None);
|
|
| ^^^^^^^^^^^^^^
|
|
|
|
error: aborting due to 1 previous error
|
|
|
|
For more information about this error, try `rustc --explain E0391`.
|