#wamr — Public Fediverse posts

creates semantic nodes and clusters #WAMR FM allgraph.ro/advanced-sea... Do you like aéPiot semantics? Donate to the aéPiot semantic platform: www.paypal.com/donate?busin...

MultiSearch Tag Explorer

creates semantic nodes and clusters #WAMR FM allgraph.ro/advanced-sea... Do you like aéPiot semantics? Donate to the aéPiot semantic platform: www.paypal.com/donate?busin...

MultiSearch Tag Explorer

I like the bootstrapping process of the #zig compiler. I'm doing a similar job with #serene's bootstrapping, too. The only difference is that I'm not going to create the #wasi interpreter myself. I'm going to utilize a small runtime like #wamr. Just include the interpreter source code in the repo, and build it with the host's C compiler, and use it to run the bootstrap compiler which is committed to the source tree in Wasm32 format, and use that to compile the self-hosted version of #serene.

I like the bootstrapping process of the #zig compiler. I'm doing a similar job with #serene's bootstrapping, too. The only difference is that I'm not going to create the #wasi interpreter myself. I'm going to utilize a small runtime like #wamr. Just include the interpreter source code in the repo, and build it with the host's C compiler, and use it to run the bootstrap compiler which is committed to the source tree in Wasm32 format, and use that to compile the self-hosted version of #serene.

I like the bootstrapping process of the #zig compiler. I'm doing a similar job with #serene's bootstrapping, too. The only difference is that I'm not going to create the #wasi interpreter myself. I'm going to utilize a small runtime like #wamr. Just include the interpreter source code in the repo, and build it with the host's C compiler, and use it to run the bootstrap compiler which is committed to the source tree in Wasm32 format, and use that to compile the self-hosted version of #serene.

I like the bootstrapping process of the #zig compiler. I'm doing a similar job with #serene's bootstrapping, too. The only difference is that I'm not going to create the #wasi interpreter myself. I'm going to utilize a small runtime like #wamr. Just include the interpreter source code in the repo, and build it with the host's C compiler, and use it to run the bootstrap compiler which is committed to the source tree in Wasm32 format, and use that to compile the self-hosted version of #serene.

I like the bootstrapping process of the #zig compiler. I'm doing a similar job with #serene's bootstrapping, too. The only difference is that I'm not going to create the #wasi interpreter myself. I'm going to utilize a small runtime like #wamr. Just include the interpreter source code in the repo, and build it with the host's C compiler, and use it to run the bootstrap compiler which is committed to the source tree in Wasm32 format, and use that to compile the self-hosted version of #serene.

Why is handling an #OS #Signal so hard in #WebAssembly ? - #WASI has a work around for us, but does it actually work?

I'm not sure - #WAMR #Wasmtime and #WASM3 might all need the new #StackSwitching proposal which was pushed to stage 2 in the #W3C today.

Check out the code samples here - https://withbighair.com/webassembly/2024/08/26/WebAssembly-and-signals.html

Why is handling an #OS #Signal so hard in #WebAssembly ? - #WASI has a work around for us, but does it actually work?

I'm not sure - #WAMR #Wasmtime and #WASM3 might all need the new #StackSwitching proposal which was pushed to stage 2 in the #W3C today.

Check out the code samples here - https://withbighair.com/webassembly/2024/08/26/WebAssembly-and-signals.html

Why is handling an #OS #Signal so hard in #WebAssembly ? - #WASI has a work around for us, but does it actually work?

I'm not sure - #WAMR #Wasmtime and #WASM3 might all need the new #StackSwitching proposal which was pushed to stage 2 in the #W3C today.

Check out the code samples here - https://withbighair.com/webassembly/2024/08/26/WebAssembly-and-signals.html

Why is handling an #OS #Signal so hard in #WebAssembly ? - #WASI has a work around for us, but does it actually work?

I'm not sure - #WAMR #Wasmtime and #WASM3 might all need the new #StackSwitching proposal which was pushed to stage 2 in the #W3C today.

Check out the code samples here - https://withbighair.com/webassembly/2024/08/26/WebAssembly-and-signals.html

WebAssembly Micro #Runtime (WAMR)

https://github.com/bytecodealliance/wasm-micro-runtime

"#WAMR is a lightweight standalone WebAssembly (Wasm) runtime with small footprint, high performance and highly configurable features for applications cross from embedded, IoT, edge to Trusted Execution Environment (TEE), [...], cloud native and so on."

Looks neat, especially the different running modes look useful:

https://bytecodealliance.github.io/wamr.dev/blog/introduction-to-wamr-running-modes/

#WASM #WebAssembly

WebAssembly Micro #Runtime (WAMR)

https://github.com/bytecodealliance/wasm-micro-runtime

"#WAMR is a lightweight standalone WebAssembly (Wasm) runtime with small footprint, high performance and highly configurable features for applications cross from embedded, IoT, edge to Trusted Execution Environment (TEE), [...], cloud native and so on."

Looks neat, especially the different running modes look useful:

https://bytecodealliance.github.io/wamr.dev/blog/introduction-to-wamr-running-modes/

#WASM #WebAssembly

WebAssembly Micro #Runtime (WAMR)

https://github.com/bytecodealliance/wasm-micro-runtime

"#WAMR is a lightweight standalone WebAssembly (Wasm) runtime with small footprint, high performance and highly configurable features for applications cross from embedded, IoT, edge to Trusted Execution Environment (TEE), [...], cloud native and so on."

Looks neat, especially the different running modes look useful:

https://bytecodealliance.github.io/wamr.dev/blog/introduction-to-wamr-running-modes/

#WASM #WebAssembly

WebAssembly Micro #Runtime (WAMR)

https://github.com/bytecodealliance/wasm-micro-runtime

"#WAMR is a lightweight standalone WebAssembly (Wasm) runtime with small footprint, high performance and highly configurable features for applications cross from embedded, IoT, edge to Trusted Execution Environment (TEE), [...], cloud native and so on."

Looks neat, especially the different running modes look useful:

https://bytecodealliance.github.io/wamr.dev/blog/introduction-to-wamr-running-modes/

#WASM #WebAssembly

WebAssembly Micro #Runtime (WAMR)

https://github.com/bytecodealliance/wasm-micro-runtime

"#WAMR is a lightweight standalone WebAssembly (Wasm) runtime with small footprint, high performance and highly configurable features for applications cross from embedded, IoT, edge to Trusted Execution Environment (TEE), [...], cloud native and so on."

Looks neat, especially the different running modes look useful:

https://bytecodealliance.github.io/wamr.dev/blog/introduction-to-wamr-running-modes/

#WASM #WebAssembly