-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
WASM: Fix System.Diagnostics.Tracing #39271
Conversation
It was missing a few signatures in wasm_m2n_invoke.g.h that caused it to fail with `WASM-ERR: CANNOT HANDLE INTERP ICALL SIG IIILIIII`
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
Its missing the changes to the generator .cs. |
the generator still lives in mono/mono. will open a PR to update the generator there. |
If you want to port it to dotnet/runtime here's the diff:
|
@@ -296,6 +296,16 @@ wasm_invoke_iiliiii (void *target_func, InterpMethodArguments *margs) | |||
|
|||
} | |||
|
|||
static void | |||
wasm_invoke_iiiliiii (void *target_func, InterpMethodArguments *margs) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does "iiiliiii" mean?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, it's the signature, i.e. it returns an int, and accepts two ints, then a long, then four ints?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
correct
It was missing a few signatures in wasm_m2n_invoke.g.h that caused it to fail with
WASM-ERR: CANNOT HANDLE INTERP ICALL SIG IIILIIII