Skip to content
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

JET.@report_trim or similar to find issues that would prevent trimming #651

Open
KristofferC opened this issue Aug 13, 2024 · 2 comments
Open

Comments

@KristofferC
Copy link

JET.@report_opt shows more things than are needed for trimming to work. A useful mode could be to restrict the printed things to only those that would prevent trimming.

@timholy
Copy link
Collaborator

timholy commented Aug 21, 2024

In the long run this could be hard to do. I think it's likely that trimming may ultimately include changes to the specialization heuristics and that might be difficult to mimic in a standard interactive session. Nevertheless the general idea is excellent, and getting at least close seems well worth the attempt.

The main practical obstacle is that currently the notion of "If a call is too dynamic to reasonably narrow down the possible call targets" requires reading the source of JuliaLang/julia#55047 to make sufficiently concrete (straightforward, but might be best to wait until it merges).

@el-oso
Copy link

el-oso commented Nov 3, 2024

Just wanted to add that I didn't know that JET.@report_opt existed. However, I have been using AllocCheck.jl instead and that had been quite useful. Specifically the dynamic dispatch errors.

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

No branches or pull requests

3 participants