Compile error 'failed to get layout for' #105809
Labels
C-bug
Category: This is a bug.
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
P-critical
Critical priority
regression-from-stable-to-nightly
Performance or correctness regression from stable to nightly.
S-has-mcve
Status: A Minimal Complete and Verifiable Example has been found for this issue
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Comments
rhomber
added
C-bug
|
@rustbot label +E-needs-mcve |
rustbot
added
the
E-needs-mcve
|
I just had a similar error in a daily CI run: https://github.com/trevyn/turbo/actions/runs/3717940350/jobs/6305763615#step:22:2010 So, probably broken between rustc 1.68.0-nightly (ec56537 2022-12-15) and 1.68.0-nightly (9c07efe 2022-12-16) |
|
I created an MCVE from use std::{future::Future, pin::Pin};
// Create a `T` without affecting analysis like `loop {}`.
fn create<T>() -> T {
loop {}
}
async fn trivial_future() {}
struct Connection<H> {
_h: H,
}
async fn complex_future<H>(conn: &Connection<H>) {
let small_fut = async move {
let _ = conn;
trivial_future().await;
};
let mut tuple = (small_fut,);
let (small_fut_again,) = &mut tuple;
let _ = small_fut_again;
}
fn main() {
let mut fut = complex_future(&Connection { _h: () });
let mut cx = create();
let future = unsafe { Pin::new_unchecked(&mut fut) };
let _ = future.poll(&mut cx);
} |
|
searched nightlies: from nightly-2022-01-01 to nightly-2022-12-17 bisected with cargo-bisect-rustc v0.6.4Host triple: x86_64-unknown-linux-gnu cargo bisect-rustc --access github --regress ice |
|
Can confirm nightly-2022-12-12 (I could try a newer one, but haven't) works. So it's a recent change that's broken things. |
|
Given the backtrace in the first post it does seem plausible that this ICE is caused by that change, but for some reason I cannot reproduce the ICE in your MCVE on my local branch for that PR. |
matthiaskrgr
added
S-has-mcve
|
Hmm is this an apple-only crash? I can't reproduce on x86_64. |
|
Just checked again, my MCVE require edition 2018. |
|
No it happens on both And the edition I am using is: edition = "2021" |
|
oh weird, I see now that this does only crash with |
This was referenced Dec 18, 2022
|
I still cannot reproduce this on my local branch even when using different |
|
I can reproduce my example with the current master branch using backtracemy config and envIt also doesn't ICE for me with |
lcnr
added
the
regression-from-stable-to-nightly
rustbot
added
the
I-prioritize
fasterthanlime
added a commit
to bearcove/loona
that referenced
this issue
Dec 19, 2022
|
hello there, had a similar error in a CI run: https://github.com/keep-starknet-strange/beerus/actions/runs/3720223159/jobs/6309558454 |
10 tasks
jackh726
added
P-critical
|
Assigning this as P-critical. We should get a fix or revert today if we can. It's getting hit a lot. |
Closed
|
I updated the compiler this morning to check and the rocket code doesn't pass compilation still. What is the expected timeframe to get this bug fixed (either with a corrective or a temporary patch as I could see in the trail)? Thanks in advance. |
Have the same problem as before. Rocket application can't be compiled with the same errors as yesterday. |
|
The revert fixing this issue has already been merged, but has missed the |
|
Simple async hello world application works on stable 1.66.0, I will keep testing it. |
Would it help if you override version to 1.66 or another one? |
|
Why is this still pinned? |
|
It made sense to keep it pinned for people who haven't updated their nightly yet and are still hitting it. But I guess we could unpin it now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Code
It's not failing in my project, but a dependency (but rocket).
Meta
Fails the same in two environments:
AND
Error output
Backtrace
As above.
The text was updated successfully, but these errors were encountered: