-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
irinterp: improve semi-concrete interpretation accuracy #52275
Conversation
@nanosoldier |
bebfaa6
to
53490cd
Compare
Your benchmark job has completed - no performance regressions were detected. A full report can be found here. |
6680dd3
to
f57a9b4
Compare
f57a9b4
to
367fb7b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. It does seem to suggest to me that we should consider how to record a bit of information on the calls whether a more precise result is possible from constprop (either because of some widening vs the return value being obviously unchangable like just return nothing
)
That sounds to be a great idea. I would like to give that a try in a separate PR. |
) By enforcing re-inference on calls with all constant arguments. While it's debatable whether this approach is the most efficient, it was the easiest choice given that `used_ssas` based on `IncrementaCompact` wasn't an option for irinterp. - fixes JuliaLang#52202 - fixes JuliaLang#50037
@KristofferC Can we backport this to 1.10 to resolve JuliaSparse/SparseArrays.jl#469 (assuming this is the correct fix for that regression)? |
By enforcing re-inference on calls with all constant arguments.
While it's debatable whether this approach is the most efficient, it was the easiest choice given that
used_ssas
based onIncrementaCompact
wasn't an option for irinterp.