-
Notifications
You must be signed in to change notification settings - Fork 136
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
Support external stacks and local function calls using local memory #460
Conversation
hawkinsw
commented
May 11, 2024
- Add support for invoking the interpreter and JIT'd code with an external stack. This feature is generally useful and will also make it easier to fuzz the runtime and check for correctness.
- Add support for local functions that use local memory. Prior to this commit, a local function could be called but could not use any local memory (without overwriting memory from another function).
6e2a4d1
to
9a42663
Compare
5bfcb6e
to
127a73e
Compare
127a73e
to
00745b7
Compare
Can you please format the code using script/format-code? It looks like there are formatting changes that are unexpected. |
Of course!! I thought that I did. Sorry!! |
9ccdf2e
to
b5a492e
Compare
I believe that I ran the formatter on the code (and did it correctly!). |
1. Add support for invoking the interpreter and JIT'd code with an external stack. This feature is generally useful and will also make it easier to fuzz the runtime and check for correctness. 2. Add support for local functions that use local memory. Prior to this commit, a local function could be called but could not use any local memory (without overwriting memory from another function). Signed-off-by: Will Hawkins <hawkinsw@obs.cr>
b5a492e
to
7208c4b
Compare
OK, it might just be possible the code wasn't formatted correctly to begin with. Which version of clang-format did you use? |
I will check!! I am constantly amazed how version-specific the formatter is! This problem occurs with another project I am working on, too. |
If you want, we can pick-up a newer version of the formatter if that helps. I think this is using the same one as eBPF-for-Windows, which is using a really old version (due to a dependency on an older version of Clang). If that is a route we want to pursue, I would suggest making the changes as a separate formatting only PR. |