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
This runtime check is expensive. Instead, we should try to generate an APPCOMB separate bytecode when applying a combinator to avoid the runtime check. The peephole optimisation should be extended to add rules with APPCOMB etc
The text was updated successfully, but these errors were encountered:
Currently, in the VM a combinator is represented on the heap using a dummy value
Represented here in the code: https://github.com/svenssonjoel/Sense-VM/blob/master/backend/src/CAM.c#L1110-L1115
Later when evaluating an
APP
bytecode a runtime check is done to determine if applying on a combinator or a closure done here: https://github.com/svenssonjoel/Sense-VM/blob/master/backend/src/CAM.c#L372-L418This runtime check is expensive. Instead, we should try to generate an
APPCOMB
separate bytecode when applying a combinator to avoid the runtime check. The peephole optimisation should be extended to add rules with APPCOMB etcThe text was updated successfully, but these errors were encountered: