Skip to content

Conversation

Noratrieb
Copy link
Member

In #100121, I removed the double normalization in the mir validator. It turns out that this outer normalization is still needed because the inner normalization erases all regions - even late bound ones that may be required for normalization sometimes.

This still needs an MCVE as a test.

Hopefully fixes #101344

r? @compiler-errors

This reverts commit 96d4137.

The outer normalization is needed because it hasn't erased late bound
lifetimes yet which is required for some normalizations.
@rustbot rustbot added the T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. label Sep 5, 2022
@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Sep 5, 2022
@compiler-errors
Copy link
Member

Hm, @Nilstrieb, I thought I mentioned I was going to put up a different version of this where we correctly normalize before erasing late-bound regions in equal_up_to_regions?

@Noratrieb
Copy link
Member Author

oh i got confused by the double negation of the message, haha

well i can close it then

@Noratrieb Noratrieb closed this Sep 5, 2022
@Noratrieb Noratrieb deleted the well-actually branch September 5, 2022 06:56
@compiler-errors
Copy link
Member

Whoops, sorry. I apologize if you wasted time on this. Still working on a minimization, but all of the examples of this ICE are incredibly complicated.

@Noratrieb
Copy link
Member Author

no problem, I didn't have anything better to do anyways :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

miri no longer builds after rust-lang/rust#101333
4 participants