I’ve been through the official API and documentation for Emscripten, but
they don’t cover the things I’m really curious about.
What I’m looking for are lower-level resources: explanations of how the
memory model works, what’s actually happening when crossing the WASM/JS
boundary, and how memory lifetimes are handled.
For example, it’s still unclear to me exactly *when* the JS barrier is
crossed or what guarantees exist around memory in cases like this:
emscripten::val Float64Array = emscripten::val::global("Float64Array");
const double* src = reinterpret_cast<const
double*>(someVectorOfDoubles.data());
emscripten::val view(emscripten::typed_memory_view(numDoubles, src));
jsArr.call<void>("set", view)
If you’ve found blog posts, talks, deep dives, or even good discussions on
this topic, I’d really appreciate any pointers.
--
You received this message because you are subscribed to the Google Groups
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/emscripten-discuss/45234e7e-43ad-4efd-b74d-17665a1e3cb1n%40googlegroups.com.
