You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: