[RFC] Log a backtrace on entrance to type inference (option 1) #58123
+27
−0
Conversation
This file contains 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
This is needed to eliminate the `Core.Compiler.Timings` module while still keeping SnoopCompile working.
This was referenced Apr 15, 2025
|
What's this back-trace used for? |
|
SnoopCompile has analysis for inference triggers to help find and eliminate dynamic dispatch. The backtrace is used to link the callee to the caller across the dynamic dispatch. |
|
I should mention that I personally think #58124 is the better design. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is needed to eliminate the
Core.Compiler.Timingsmodule while still keeping SnoopCompile working.This is one mechanism to add a backtrace to each entrance to inference. An alternative approach is presented in #58124. Only one of these should be merged.