|
| 1 | +// Copyright 2013 The Rust Project Developers. See the COPYRIGHT |
| 2 | +// file at the top-level directory of this distribution and at |
| 3 | +// http://rust-lang.org/COPYRIGHT. |
| 4 | +// |
| 5 | +// Licensed under the Apache License, Version 2.0 <LICENSE-APACHE or |
| 6 | +// http://www.apache.org/licenses/LICENSE-2.0> or the MIT license |
| 7 | +// <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your |
| 8 | +// option. This file may not be copied, modified, or distributed |
| 9 | +// except according to those terms. |
| 10 | + |
| 11 | +/*! |
| 12 | + * On x86_64-linux-gnu and possibly other platforms, structs get 8-byte "preferred" alignment, |
| 13 | + * but their "ABI" alignment (i.e., what actually matters for data layout) is the largest alignment |
| 14 | + * of any field. (Also, u64 has 8-byte ABI alignment; this is not always true). |
| 15 | + * |
| 16 | + * On such platforms, if monomorphize uses the "preferred" alignment, then it will unify |
| 17 | + * `A` and `B`, even though `S<A>` and `S<B>` have the field `t` at different offsets, |
| 18 | + * and apply the wrong instance of the method `unwrap`. |
| 19 | + */ |
| 20 | + |
| 21 | +struct S<T> { i:u8, t:T } |
| 22 | +impl<T> S<T> { fn unwrap(self) -> T { self.t } } |
| 23 | +struct A((u32, u32)); |
| 24 | +struct B(u64); |
| 25 | + |
| 26 | +pub fn main() { |
| 27 | + static Ca: S<A> = S { i: 0, t: A((13, 104)) }; |
| 28 | + static Cb: S<B> = S { i: 0, t: B(31337) }; |
| 29 | + assert_eq!(*(Ca.unwrap()), (13, 104)); |
| 30 | + assert_eq!(*(Cb.unwrap()), 31337); |
| 31 | +} |
0 commit comments