P
one question guys, what can be the limitations of compiling a runtime into webasm? the filesystem, threading, and other syscalls (that arent implemented for that platform) or is it possible to find incompatibilities in the runtime itself?
Size: a a a
2019 July 18
P
I have read about transition of python to webasm, and the main problems were that, but do you know any other runtime?
VG
I didn't know that, I thought it was c++/CLI c# vb.net and asp.net and then f#, have you ever used jscript.net?
Yup. I even maged to compile some CoffeeScript v1 code into it with some manual fixing. Not stellar, but still ECMAScript we all love.
P
Yup. I even maged to compile some CoffeeScript v1 code into it with some manual fixing. Not stellar, but still ECMAScript we all love.
nice
MV
one question guys, what can be the limitations of compiling a runtime into webasm? the filesystem, threading, and other syscalls (that arent implemented for that platform) or is it possible to find incompatibilities in the runtime itself?
It depends on a runtime. E.g. it difficult to compile some goto/setjmp/longjump of C to wasm due to the structered control flow. You can also check marvelous WASI that provide a possibility to compile C/C++ to wasm with the limited set of imported syscalls.
P
It depends on a runtime. E.g. it difficult to compile some goto/setjmp/longjump of C to wasm due to the structered control flow. You can also check marvelous WASI that provide a possibility to compile C/C++ to wasm with the limited set of imported syscalls.
but goto and family are just jumps, aren't they contemplated in wasm?
P
also, LLVM seems to be supporting wasm, or at least I heard that, am I right?
P
what do you mean by imported syscalls?
P
how wasm plans to solve syscalls problem?
P
at the end there will be an OS or a browser on as a platform
P
syscalls is an essential part
MV
but goto and family are just jumps, aren't they contemplated in wasm?
In wasm you can jump only to the predefined points called blocks. You can find more info in spec or in the article
P
without them you cannot interact with the platform
P
In wasm you can jump only to the predefined points called blocks. You can find more info in spec or in the article
I see, thanks dude
MV
In this article you can find almost all answers except about llvm
MV
And it is more easy to read compare to the wasm spec
MV
also, LLVM seems to be supporting wasm, or at least I heard that, am I right?
Yes, and since 8.0.0 this support isn't experimental, but only llvm can't solve the problem with OS interaction. You shoud have some special libc (you can find more details on the introduction here https://medium.com/fluence-network/porting-redis-to-webassembly-with-clang-wasi-af99b264ca8) and sysroot.
P
In this article you can find almost all answers except about llvm
ty dude
P
Yes, and since 8.0.0 this support isn't experimental, but only llvm can't solve the problem with OS interaction. You shoud have some special libc (you can find more details on the introduction here https://medium.com/fluence-network/porting-redis-to-webassembly-with-clang-wasi-af99b264ca8) and sysroot.
I see, thanks