summaryrefslogtreecommitdiffstats
path: root/src/test/ui/print_type_sizes/padding.rs
diff options
context:
space:
mode:
Diffstat (limited to 'src/test/ui/print_type_sizes/padding.rs')
-rw-r--r--src/test/ui/print_type_sizes/padding.rs34
1 files changed, 34 insertions, 0 deletions
diff --git a/src/test/ui/print_type_sizes/padding.rs b/src/test/ui/print_type_sizes/padding.rs
new file mode 100644
index 000000000..d1acad16d
--- /dev/null
+++ b/src/test/ui/print_type_sizes/padding.rs
@@ -0,0 +1,34 @@
+// compile-flags: -Z print-type-sizes
+// build-pass
+
+// This file illustrates how padding is handled: alignment
+// requirements can lead to the introduction of padding, either before
+// fields or at the end of the structure as a whole.
+//
+// It avoids using u64/i64 because on some targets that is only 4-byte
+// aligned (while on most it is 8-byte aligned) and so the resulting
+// padding and overall computed sizes can be quite different.
+
+#![feature(start)]
+#![allow(dead_code)]
+
+struct S {
+ a: bool,
+ b: bool,
+ g: i32,
+}
+
+enum E1 {
+ A(i32, i8),
+ B(S),
+}
+
+enum E2 {
+ A(i8, i32),
+ B(S),
+}
+
+#[start]
+fn start(_: isize, _: *const *const u8) -> isize {
+ 0
+}