Thanks,
The above looks cool.
Basically copy-pasting
clang/lib/Interpreter/Wasm.cpp
Yeah, one of the things that I possibly haven’t addressed in that file is not exposing the generated xx.o/wasm files.
I see the same in the demo above (in the file system on the left)
For our C++ Kernel, we just hide it in Jupyterlite’s tmp directory provided in the virtual file system . Not sure that’s the best approach though and hence it lives as a patch in our llvm/clang recipe on emscripten-forge. Let me know if you find a better approach here.
Also feel free to host your wasm builds for MLIR/MLIR-python bindings as recipes on emscripten-forge, so that you won’t have to fetch them at runtime while in Jupyterlite and can add them to your wasm environment before serving.