-
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 related to constant evaluation timeout #112748
Labels
C-bug
Category: This is a bug.
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Comments
claytonwramsey
added
C-bug
Category: This is a bug.
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
labels
Jun 17, 2023
cc @oli-obk |
I just checked - I was able to cause this error to occur in 1.72 nightly but not in 1.70 stable. |
GuillaumeGomez
added a commit
to GuillaumeGomez/rust
that referenced
this issue
Jun 22, 2023
Stop hiding const eval limit in external macros fixes rust-lang#112748 We don't emit a hard error if there was a previous deny lint triggering with the same message. If that lint ends up not being emitted, we ICE and don't emit an error either.
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Jun 23, 2023
Stop hiding const eval limit in external macros fixes rust-lang#112748 We don't emit a hard error if there was a previous deny lint triggering with the same message. If that lint ends up not being emitted, we ICE and don't emit an error either.
GuillaumeGomez
added a commit
to GuillaumeGomez/rust
that referenced
this issue
Jun 23, 2023
Stop hiding const eval limit in external macros fixes rust-lang#112748 We don't emit a hard error if there was a previous deny lint triggering with the same message. If that lint ends up not being emitted, we ICE and don't emit an error either.
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Jun 23, 2023
Stop hiding const eval limit in external macros fixes rust-lang#112748 We don't emit a hard error if there was a previous deny lint triggering with the same message. If that lint ends up not being emitted, we ICE and don't emit an error either.
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Jun 23, 2023
Stop hiding const eval limit in external macros fixes rust-lang#112748 We don't emit a hard error if there was a previous deny lint triggering with the same message. If that lint ends up not being emitted, we ICE and don't emit an error either.
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Jun 23, 2023
Stop hiding const eval limit in external macros fixes rust-lang#112748 We don't emit a hard error if there was a previous deny lint triggering with the same message. If that lint ends up not being emitted, we ICE and don't emit an error either.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C-bug
Category: This is a bug.
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Minimum example:
I have a full project where I was able to consistently cause this error. It seems to be related to the timeout on constant evaluation. For my project which consistently has the error, check here.
For some reason, annotating
ROOK_ATTACKS_TABLE
with#[allow(long_running_const_eval)]
prevents this error.Meta
rustc --version --verbose
:Error output
Backtrace
The text was updated successfully, but these errors were encountered: