Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upICE: "broken MIR in DefId" when assigning mismatched closure to `FnMut` #53448
Comments
This was referenced Aug 19, 2018
matthewjasper
assigned
matthewjasper
and unassigned
matthewjasper
Aug 21, 2018
earthengine
changed the title
Compiler unexpected panic when MIRI verification fail in a certain situation
ICE with code irrelevant message - cannot access a scoped thread local variable without calling `set` first
Aug 22, 2018
This comment has been minimized.
This comment has been minimized.
|
New error messages after PR #53624 :
|
oli-obk
added
the
I-ICE
label
Aug 31, 2018
matthewjasper
added
A-NLL
NLL-complete
and removed
NLL-complete
labels
Sep 2, 2018
This comment has been minimized.
This comment has been minimized.
|
Marking with A-NLL since this is an issue with MIR typeck, even though this happens without nll. |
pnkfelix
added
T-compiler
A-mir
labels
Sep 18, 2018
This comment has been minimized.
This comment has been minimized.
|
self-assigning for preliminary investigation |
pnkfelix
self-assigned this
Sep 18, 2018
This comment has been minimized.
This comment has been minimized.
|
Discussed with @nikomatsakis. He theorizes it is part of collection of bugs around normalization. Its not really an A-NLL thing. So I'm removing that label. |
pnkfelix
removed
the
A-NLL
label
Sep 25, 2018
pnkfelix
changed the title
ICE with code irrelevant message - cannot access a scoped thread local variable without calling `set` first
ICE: "broken MIR in DefId" when assigning mismatched closure to `FnMut`
Oct 4, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
earthengine commentedAug 17, 2018
•
edited by pnkfelix
The following code
causes panic with message
which is irrelevant to the code. Simply modify
link_binaryfunction in src\librustc_codegen_llvm\back\link.rs to make it panic before return, will then output some result that saysThis is a variation of #53420 aka #29997, but is more serious and we should fix this first to make it at least emit the real error.
The proper fix of this issue, is NOT to make the code above compile; instead, it should give ICE with proper messages instead of something irrelevant so that we ensure we can get useful information from ICEs all the time, and the ICE is to be fixed after #53420 aka #29997.