-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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 in 1.30 and 1.31 #55846
Comments
Uh, this looks like a regression. What's the library? |
It's currently a private library. It's a constraint programming solver.
Dan
…On Sat, Nov 10, 2018, 4:55 PM Pietro Albini ***@***.***> wrote:
Uh, this looks like a regression. What's the library?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#55846 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AX1QPYIWAd_cCVaq_E0bfvmPXgBK4FYvks5ut0tagaJpZM4YX-37>
.
|
Can you reduce the bug to a subset of the library you can publish? Unfortunately it's hard for us to investigate an error without the code that's causing it. cc @rust-lang/compiler |
Yes, I'll try later today. Thanks.
…On Sat, Nov 10, 2018, 5:10 PM Pietro Albini ***@***.***> wrote:
Can you reduce the bug to a subset of the library you can publish?
Unfortunately it's hard for us to investigate an error without the code
that's causing it.
cc @rust-lang/compiler <https://github.com/orgs/rust-lang/teams/compiler>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#55846 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AX1QPSag6a2c_7m3ABfbY93m7TbSjcPSks5ut07ggaJpZM4YX-37>
.
|
@nikomatsakis @oli-obk This looks like either trait system or const-evaluation. |
Here is a single file example where it occurs.
Dan
…On Sat, Nov 10, 2018 at 5:10 PM Pietro Albini ***@***.***> wrote:
Can you reduce the bug to a subset of the library you can publish?
Unfortunately it's hard for us to investigate an error without the code
that's causing it.
cc @rust-lang/compiler <https://github.com/orgs/rust-lang/teams/compiler>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#55846 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AX1QPSag6a2c_7m3ABfbY93m7TbSjcPSks5ut07ggaJpZM4YX-37>
.
|
Below is a rust file with the error. |
No longer repros in beta or nightly, present in stable. Would it be reasonable to backport the fix (once we identify it) to stable? |
Identifying the nightly where this was fixed via bissection would be a good start to determining what fixed it (and thus evaluating whether a backport to stable is reasonable). But a problem has to meet a pretty high bar to justify a backport to the stable channel... a rare ICE may not cut it |
This is now fixed, but we need to make sure it won't regress in the future. Currently the test case is quite large: #55846 (comment). If someone wants to fix this, you just need to try to find the smallest test case you can that still fails on the current version of stable and add it to the test suite in |
triage. Since this fixed and just needs a test, tagging as P-medium. |
Add regression test for ICE Fixes rust-lang#55846 with a minimal (or as best as I can manage) test case. I tested this against 1.30.0 manually to confirm it crashes. The issue seemed to have something to do with associated types. It's possible someone with more knowledge can shrink the test case down further, or make it clearer.
This library compiled without issue in rust versions prior to 1.30.
The text was updated successfully, but these errors were encountered: