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

AbstractInterpreter: remove dead OptimizationState handling in inlining_policy #43378

Merged
merged 1 commit into from
Dec 10, 2021

Conversation

aviatesk
Copy link
Member

@aviatesk aviatesk commented Dec 9, 2021

NativeInterpreter never hits this case, and external interpreters can
always define their own inlining_policy in order to use whichever
information they are caching.

`NativeInterpreter` never hits this case, and external interpreters can
always define their own `inlining_policy` in order to use whichever
information they are caching.
@aviatesk aviatesk changed the title optimizer: remove dead OptimizationState handling in inlining_policy AbstractInterpreter: remove dead OptimizationState handling in inlining_policy Dec 9, 2021
@aviatesk aviatesk requested a review from Keno December 9, 2021 05:00
@aviatesk aviatesk merged commit 524bca4 into master Dec 10, 2021
@aviatesk aviatesk deleted the avi/inlining-policy branch December 10, 2021 22:01
LilithHafner pushed a commit to LilithHafner/julia that referenced this pull request Feb 22, 2022
…cy` (JuliaLang#43378)

`NativeInterpreter` never hits this case, and external interpreters can
always define their own `inlining_policy` in order to use whichever
information they are caching.
LilithHafner pushed a commit to LilithHafner/julia that referenced this pull request Mar 8, 2022
…cy` (JuliaLang#43378)

`NativeInterpreter` never hits this case, and external interpreters can
always define their own `inlining_policy` in order to use whichever
information they are caching.
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.

1 participant