File: mir_const_prop_tuple_field_reorder.rs

package info (click to toggle)
rustc 1.88.0%2Bdfsg1-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 934,128 kB
  • sloc: xml: 158,127; python: 36,062; javascript: 19,855; sh: 19,700; cpp: 18,947; ansic: 12,993; asm: 4,792; makefile: 690; lisp: 29; perl: 29; ruby: 19; sql: 11
file content (27 lines) | stat: -rw-r--r-- 627 bytes parent folder | download | duplicates (16)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
//@ compile-flags: -Z mir-opt-level=3
//@ build-pass
#![crate_type="lib"]

// This used to ICE: const-prop did not account for field reordering of scalar pairs,
// and would generate a tuple like `(0x1337, VariantBar): (FooEnum, isize)`,
// causing assertion failures in codegen when trying to read 0x1337 at the wrong type.

pub enum FooEnum {
    VariantBar,
    VariantBaz,
    VariantBuz,
}

pub fn wrong_index() -> isize {
    let (_, b) = id((FooEnum::VariantBar, 0x1337));
    b
}

pub fn wrong_index_two() -> isize {
    let (_, (_, b)) = id(((), (FooEnum::VariantBar, 0x1338)));
    b
}

fn id<T>(x: T) -> T {
    x
}