-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Incremental compilation ICE: Found unstable fingerprints for predicates_of(dicom_core[4803]::value::DicomValueType) #88420
Labels
A-incr-comp
Area: Incremental compilation
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
Got a seemingly similar ICE, here's the output:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-incr-comp
Area: Incremental compilation
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.
I triggered ICE through incremental compilation (tracker issue #84970) while working on DICOM-rs. This could be a similar problem to #88318. Unlike what was reported in #84341,
predicates_of
was called on a trait in the same workspace.Code
I was unable to reproduce this a second time in a fresh working space. When the ICE occurred, I saved the state of the project in this branch. Then I tried to recall all the steps I had done since the previous revision, around this order:
dicom_encoding::text::DynamicTextCodec
dicom_encoding::text::SpecificCharacterSet::codec
impl TextCodec for SpecificCharacterSet
, methods implemented by matching on self and picking the right text codec type.SpecificCharacterSet::GB18030 = SpecificCharacterSet::Gb18030
GB18030
toGb18030
, update the name in the rest of the module.codec()
indicom_encoding::text::tests
But tracing these steps again did not trigger any ICE. Rust-analyzer was running, which suddenly started failing all checking requests. The ICE only occurs on
cargo check
.Meta
Latest stable.
cargo +beta check
yielded no ICE, but it could just be the consequence of checking the code from scratch.rustc --version --verbose
:Error output
Backtrace
Backtrace from rust-analyzer
The text was updated successfully, but these errors were encountered: