Hi, On Fri, Sep 20, 2024 at 9:36 PM Dennis Snell <dennis.sn...@automattic.com> wrote:
> > On Sep 20, 2024, at 1:21 PM, Jakub Zelenka <bu...@php.net> wrote: > > Hi, > > On Fri, Sep 20, 2024 at 6:32 PM Dennis Snell <dennis.sn...@automattic.com> > wrote: > >> >> My goal in sharing here is to help better represent my own perspective of >> WordPress’ needs based on what I’ve seen. It’s long been on my list to >> propose a WASM RFC, but because I personally haven’t had the priority >> available to get an implementation working I haven’t done so. It’s my >> impression from the documentation that the purpose of these email threads >> w.r.t. RFCs is to gather interest and input before any RFC would be put >> together, to hold these discussions before anyone commits any major time to >> it. >> > > Is your objective to support building PHP to wasm32-wasi target like it > was proposed here: https://github.com/php/php-src/pull/10457? If so, the > main issue with that was inability to do the zend_bailout as wasm does not > support currently support setjmp and longjmp. Otherwise it's mostly about > disabling some functionality. > > > It’s the other way around. We’ve been having a great time already building > PHP as a WASM binary - > Ah ok I just did a bit of research and checking your wordpress-playground and it uses emscripten which actually integrates extensions to WASM (currentl proposed https://github.com/WebAssembly/exception-handling ) or it can JavaScript based support as described in https://emscripten.org/docs/porting/setjmp-longjmp.html . So it's not actually an issue in your case. Officially PHP can still cannot be build to the official wasm32-wasi target but as I understand it's not such a big issue because there are already viable alternatives. Cheers Jakub
