rust/tests/ui/layout/enum.stderr

error: align: AbiAlign { abi: Align(2 bytes) }
  --> $DIR/enum.rs:9:1
   |
LL | enum UninhabitedVariantAlign {
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

error: size: Size(16 bytes)
  --> $DIR/enum.rs:15:1
   |
LL | enum UninhabitedVariantSpace {
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

error: abi: ScalarPair(Initialized { value: Int(I8, false), valid_range: 0..=1 }, Initialized { value: Int(I8, false), valid_range: 0..=255 })
  --> $DIR/enum.rs:21:1
   |
LL | enum ScalarPairDifferingSign {
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

error: aborting due to 3 previous errors
Remove rustc's notion of "preferred" alignment AKA `__alignof` In PR 90877 T-lang decided not to remove `intrinsics::pref_align_of`. However, the intrinsic and its supporting code 1. is a nightly feature, so can be removed at compiler/libs discretion 2. requires considerable effort in the compiler to support, as it necessarily complicates every single site reasoning about alignment 3. has been justified based on relevance to codegen, but it is only a requirement for C++ (not C, not Rust) stack frame layout for AIX, in ways Rust would not consider even with increased C++ interop 4. is only used by rustc to overalign some globals, not correctness 5. can be adequately replaced by other rules for globals, as it mostly affects alignments for a few types under 16 bytes of alignment 6. has only one clear benefactor: automating C -> Rust translation for GNU extensions like `__alignof` 7. such code was likely intended to be `alignof` or `_Alignof`, because the GNU extension is a "false friend" of the C keyword, which makes the choice to support such a mapping very questionable 8. makes it easy to do incorrect codegen in the compiler by its mere presence as usual Rust rules of alignment (e.g. `size == align * N`) do not hold with preferred alignment The implementation is clearly damaging the code quality of the compiler. Thus it is within the compiler team's purview to simply rip it out. If T-lang wishes to have this intrinsic restored for c2rust's benefit, it would have to use a radically different implementation that somehow does not cause internal incorrectness. Until then, remove the intrinsic and its supporting code, as one tool and an ill-considered GCC extension cannot justify risking correctness. Because we touch a fair amount of the compiler to change this at all, and unfortunately the duplication of AbiAndPrefAlign is deep-rooted, we keep an "AbiAlign" type which we can wean code off later. 2025-02-11 22:09:16 -08:00			`error: align: AbiAlign { abi: Align(2 bytes) }`
rustc_abi: audit uses of is_zst; fix a case of giving an enum insufficient alignment 2023-08-27 18:01:05 +02:00			`--> $DIR/enum.rs:9:1`
			`\|`
			`LL \| enum UninhabitedVariantAlign {`
			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^`

			`error: size: Size(16 bytes)`
			`--> $DIR/enum.rs:15:1`
			`\|`
			`LL \| enum UninhabitedVariantSpace {`
			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^`

fix test failure due to differing u64 alignment on different targets 2024-02-28 18:48:14 -05:00			`error: abi: ScalarPair(Initialized { value: Int(I8, false), valid_range: 0..=1 }, Initialized { value: Int(I8, false), valid_range: 0..=255 })`
allow using scalarpair with a common prim of ptr/ptr-sized-int 2024-02-27 00:09:12 -05:00			`--> $DIR/enum.rs:21:1`
			`\|`
			`LL \| enum ScalarPairDifferingSign {`
			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^`

			`error: aborting due to 3 previous errors`
rustc_abi: audit uses of is_zst; fix a case of giving an enum insufficient alignment 2023-08-27 18:01:05 +02:00