-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Internal compiler error related to sizing of unboxes closures #16791
Labels
A-closures
Area: Closures (`|…| { … }`)
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
Comments
huonw
added
O-Arm
Target: 32-bit Arm processors (armv6, armv7, thumb...), including 64-bit Arm in AArch32 state
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
A-closures
Area: Closures (`|…| { … }`)
labels
Sep 7, 2014
huonw
removed
the
O-Arm
Target: 32-bit Arm processors (armv6, armv7, thumb...), including 64-bit Arm in AArch32 state
label
Sep 7, 2014
This seems to be due to the |
I'm working on plumbing |
This was referenced Oct 18, 2014
bkoropoff
added a commit
to bkoropoff/rust
that referenced
this issue
Oct 28, 2014
bors
added a commit
that referenced
this issue
Oct 28, 2014
…osures, r=nikomatsakis This allows unboxed closures that reference free type/region parameters to be monomorphized correctly in trans. It was necessary to make `ty_unboxed_closure` carry around a `Substs` to accomplish this. Plumbing this through typeck revealed several areas where type/region parameters in unboxed closure types are possibly not being handled correctly. Since my goal was just to fix trans, I decided to leave FIXME comments on areas that still need attention and seek feedback on the best way to clean them up, possibly as a follow-up PR. Closes #16791
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-closures
Area: Closures (`|…| { … }`)
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
The text was updated successfully, but these errors were encountered: