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

Representing entering inlined functions #32

Open
veniger opened this issue Jun 27, 2023 · 1 comment
Open

Representing entering inlined functions #32

veniger opened this issue Jun 27, 2023 · 1 comment

Comments

@veniger
Copy link

veniger commented Jun 27, 2023

As proposed by the format, information about the function that is about to be jumped into will be attached to the jump instruction itself. In case of inline-ed functions we don't have the jump instruction to rely on, so we should try to find an another way to represent it if possible.

One of the possible solutions could be data "in between" instructions, adding additional information. This could also handle the end (return) of inline functions, since that jump is also removed.

@veniger
Copy link
Author

veniger commented Jun 27, 2023

This topic requires additional discussion, particularly on finding ways of representing parts of code that are affected by inline functions and identifying ways to calculate arguments to the function being inline-ed.

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

1 participant