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

Computed jump in VM #837

Open
ypiguet-epfl opened this issue Feb 16, 2018 · 0 comments
Open

Computed jump in VM #837

ypiguet-epfl opened this issue Feb 16, 2018 · 0 comments

Comments

@ypiguet-epfl
Copy link
Collaborator

The current VM seems to support the following feature: one can jump to a stored or computed address by pushing a displacement onto the stack and returning from it (ASEBA_BYTECODE_SUB_RET).

To allow third-party compilers to benefit from it to do things like function pointers, virtual methods, or multitasking using an alternative return stack (the stack pointer is unfortunately reset in function AsebaVMSetupEvent), I request a firm commitment to keep this capability in future versions of the VM and in tools involved with bytecode (i.e. keep a single stack for data and return addresses and don't reject code using it), or to offer an alternative way offering equivalent functionality.

See #777 for the reasons I'm making this request.

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