Reset the local inference cache before standalone re-inference.#17
Merged
Conversation
The callee walk in `typeinf!` re-infers callees via `typeinf_code` on the same interpreter that ran the root inference cascade. The interpreter-local cache can still hold tombstoned (LimitedAccuracy) const-prop results from that deeper context, suppressing const-prop that would succeed in the standalone entry and storing under-optimized source (e.g. unfolded Symbol dispatch, failing GPU IR validation; JuliaGPU/CUDA.jl#3185). Clear the cache before each re-inference, matching the runtime's fresh-interpreter-per-entry behavior. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The callee walk in
typeinf!re-infers callees viatypeinf_codeon the same interpreter that ran the root inference cascade. The interpreter-local cache can still hold tombstoned (LimitedAccuracy) const-prop results from that deeper context, suppressing const-prop that would succeed in the standalone entry and storing under-optimized source (e.g. unfolded Symbol dispatch, failing GPU IR validation; JuliaGPU/CUDA.jl#3185). Clear the cache before each re-inference, matching the runtime's fresh-interpreter-per-entry behavior.