k
does quick.js support arm?
Size: a a a
2019 July 17
P
it doesn't depend on the architecture
P
that's solved by gcc or clang (or ecmascripten)
P
this is the output of a hello world
ҪҸ
i need same thing but for wasm
ҪҸ
or just arm baseline compiler or small footprint interpreter
ҪҸ
can’t wait for cranelift arm support
MV
it can compile js files into c files embedding the bytecode inside
But it isn't translate or transform js to wasm, is it? It just compiles js engine with embedded js code into wasm and then inside wasm the engine interprets this js code.
MV
no idea about it, do you have references?
P
But it isn't translate or transform js to wasm, is it? It just compiles js engine with embedded js code into wasm and then inside wasm the engine interprets this js code.
it converts js code to binary or c files
P
it embeds the bytecode into c files and uses the runtime to launch it
P
it can also act as a jit
MV
but it seems that NectarJS isn't product ready
P
wasm is unrelated but you can compile the c code to wasm with ecmascripten
P
but it seems that NectarJS isn't product ready
quickjs is, it passes all tests from es2019 specification
MV
it embeds the bytecode into c files and uses the runtime to launch it
I mean that there are two ways: 1. you can directly translate a code on some language (not only JS) to wasm like the AssemblyScript approach and 2. you can translate to wasm the interpreter and then run a code on it.
P
wasm is unrelated but you can compile the c code to wasm with ecmascripten
which wasn't possible before (or at least without doing it directly to c)
P
I mean that there are two ways: 1. you can directly translate a code on some language (not only JS) to wasm like the AssemblyScript approach and 2. you can translate to wasm the interpreter and then run a code on it.
you can do both with QuickJS
P
you can compile the compiler to wasm and jit js code later on or compile js code to c code from browser