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
{{ message }}
This repository has been archived by the owner on Oct 20, 2024. It is now read-only.
When a jump table is used inside a macro, and the macro is called more than once, the first time the macro is called, it jumps to the jump table on the second macro instance.
In this example, it can be seen that only one increment is performed. This happens because the first time DOES_A_JUMP is called, it loads the jump table that belongs to the second instance.
When a jump table is used inside a macro, and the macro is called more than once, the first time the macro is called, it jumps to the jump table on the second macro instance.
In this example, it can be seen that only one increment is performed. This happens because the first time
DOES_A_JUMP
is called, it loads the jump table that belongs to the second instance.If we add an entry point, we can see it in the generated bytecode:
Both jumptables end up with the same jump destinations.
The text was updated successfully, but these errors were encountered: