Evaluation order in struct expressions can be incorrect

Summary

https://doc.rust-lang.org/reference/expressions.html#r-expr.operand-order

GCCRS appears to evaluate child expressions of struct expressions in field definition order, not left to right inside the expression.

Reproducer

#![no_core]

extern "C" {
    fn first_call() -> i32;
    fn second_call() -> i32;
}

pub fn get_0() -> i32 {
    struct S {
        a: i32,
        b: i32
    };

    let x = unsafe {
        S { b: first_call (), a: second_call () }
    };

    x.a
}

Does the code make use of any (1.49) nightly feature ?

• Nightly

Godbolt link

https://godbolt.org/z/9hEoM8YGd

Actual behavior

second_call is called first

Expected behavior

first_call is called first

GCC Version

308bc94241b95066f12818dc63b9f7b26c0b07f8

Start with the Rust Reference section on operand order and reproduce the issue using the provided Rust example or Godbolt link. Trace how gccrs evaluates child expressions in struct expressions, then verify that the reproducer calls first_call before second_call as expected.