-
Notifications
You must be signed in to change notification settings - Fork 786
PostEmscripten: Preserve __em_js__ exports (and data) in side modules #5780
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
Conversation
This works in a similar way to EM_ASM. See #18228. Depends on WebAssembly/binaryen#5780
Added some testing |
(export "__start_em_asm" (global $em_asm_start)) | ||
;; CHECK: (export "__stop_em_asm" (global $em_asm_stop)) | ||
(export "__stop_em_asm" (global $em_asm_stop)) | ||
(export "__start_em_js" (global $em_js_start)) |
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.
Why is this one not preserved in the output?
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.
For EM_ASM we use the global start/stop symbols and split the resulting string on NULL.
For EM_JS each string is exported via its own global export e.g. __em_js__foo
so we don't need the start/stop symbols.
This works in a similar way to EM_ASM. See #18228. Depends on WebAssembly/binaryen#5780
This works in a similar way to EM_ASM. See #18228. Depends on WebAssembly/binaryen#5780
This works in a similar way to EM_ASM. See #18228. Depends on WebAssembly/binaryen#5780
This works in a similar way to EM_ASM. See #18228. Depends on WebAssembly/binaryen#5780
This works in a similar way to EM_ASM. See #18228. Depends on WebAssembly/binaryen#5780
This works in a similar way to EM_ASM. See #18228. Depends on WebAssembly/binaryen#5780
No description provided.