On Mon, Feb 25, 2019 at 5:28 PM J Decker <d3c...@gmail.com> wrote: > I'm not familiar with these, but do know about HEAP8, HEAP32, etc. :) The > code I get generated does not have either of those symbols; it might be to > support some C++ structure you have... All the code I compiled was actually > C. The basic C library support all works as expected (fopen for instance). >
The code being compiled into wasm in this case isn't C (or C++), but Halide <http://halide-lang.org/>, which interfaces directly with LLVM. Emscripten is not involved at all (and I'd prefer to keep it that way, if possible). The readme here shows basically how to use _gsm_create, _gsm_decode and > _gsm_encode. > https://github.com/d3x0r/gsm-wasm > Thanks for the suggestion, but this is specifically what I'm hoping to *avoid* (ie, writing JavaScript adaptor code just to be able to allow C++ and wasm-generated code to interoperate). -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
