Skip to content

Conversation

@timholy
Copy link
Member

@timholy timholy commented Apr 15, 2025

This is needed to eliminate the Core.Compiler.Timings module 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.

This is needed to eliminate the `Core.Compiler.Timings` module while
still keeping SnoopCompile working.
@topolarity
Copy link
Member

What's this back-trace used for?

@timholy
Copy link
Member Author

timholy commented Apr 15, 2025

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.

@timholy
Copy link
Member Author

timholy commented Apr 15, 2025

I should mention that I personally think #58124 is the better design.

@timholy
Copy link
Member Author

timholy commented Jul 17, 2025

Close in preference to #58124

@timholy timholy closed this Jul 17, 2025
@timholy timholy deleted the teh/snoopinf_backtrace1 branch July 17, 2025 17:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants