Conversation
|
Any chance that this will allow for Instance.Memory access? I am working on making possible to use llhttp with txiki as an http protocol parser. This will make it possible txiki to act as efficient http server. |
478a788 to
97927cb
Compare
Yes, I think so. Once the replacement lands I plan to tackle the API gap. |
79a6a53 to
ea9ac0c
Compare
CMakeLists.txt
Outdated
| set(WAMR_BUILD_REF_TYPES 0) | ||
| set(WAMR_BUILD_BULK_MEMORY 0) |
There was a problem hiding this comment.
I am not sure how WAMR_BUILD_REF_TYPES and WAMR_BUILD_BULK_MEMORY affect the tjs wamr bindings, but will there be a way to toggle on these two when building? wasi-sdk emits code that uses reference-types and bulk memory by default and I have no idea how or even if I can configure clang (and the linker) to not use these extensions..
There was a problem hiding this comment.
..I am still in the process of understanding how cmake works and how to fiddle with clang toolchain configs :(. So probably I am missing something.
There was a problem hiding this comment.
The idea is to have sane defaults, I can look into those, thanks for the heads up!
Closes: #652
Closes: #652