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

Not possible to specify an opcode directly in hex #110

Closed
vyzo opened this issue Sep 10, 2022 · 2 comments
Closed

Not possible to specify an opcode directly in hex #110

vyzo opened this issue Sep 10, 2022 · 2 comments

Comments

@vyzo
Copy link

vyzo commented Sep 10, 2022

I would like to be able to test extension opcodes, that are otherwise invalid, using the assembler.
Unfortunately the parser does not seem to provide any escape mechanism for directly embedding opcodes in the program.

For example, say that I am defining in my EVM impl semantics for the 0xb0 opcode,
I would like to be able to just assemble a program that says 0xb0 or ins(0xb0), but the parser fails me.

@vyzo
Copy link
Author

vyzo commented Sep 10, 2022

Note that the request here is a generic way to specify arbitrary opcodes in the assembled program.
A builtin macro like ins(0xXX) or just hex(0xXX) will do!

@SamWilsn
Copy link
Contributor

Thanks for reporting!

Duplicate of: #106

@SamWilsn SamWilsn closed this as not planned Won't fix, can't repro, duplicate, stale Oct 18, 2022
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

2 participants