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

Ensure we keep receiver type information when TFA de-virtualizes calls #35179

Open
mkustermann opened this issue Nov 15, 2018 · 0 comments
Open
Labels
area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends.

Comments

@mkustermann
Copy link
Member

When TFA de-virtualizes instance calls into static calls we might loose the inferred type information on the receiver.

Currently we have ad-hoc code for strengthening the type of the receiver based on the target of a static call instruction, e.g. in the AOT call specializer . We should ensure the type information is already attached from the very beginning, instead of "re-computing" based on the target of a static call. Also the TFA might have a more precise receiver type than the we can re-compute based on the target (since that can be in a super class).

@mraleph @alexmarkov

@mkustermann mkustermann added the area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. label Nov 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends.
Projects
None yet
Development

No branches or pull requests

1 participant