binaryen
wasi-sdk
Our great sponsors
binaryen | wasi-sdk | |
---|---|---|
14 | 11 | |
7,099 | 1,131 | |
1.7% | 4.2% | |
9.8 | 7.6 | |
6 days ago | 2 days ago | |
WebAssembly | Shell | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
binaryen
-
Bring garbage collected programming languages efficiently to WebAssembly
The Binaryen wasm optimizer (mentioned in the article) is always open for contributions,
https://github.com/WebAssembly/binaryen
-
Random Testing of WebAssembly Implementations Using Semantically Valid Programs
The end of the related work section cites both wasm-smith and the Binaryen fuzzer (https://github.com/WebAssembly/binaryen/wiki/Fuzzing) and says, "They both provide a fuzzer that turns a stream of bytes into a WebAssembly module in order to test implementations. Their fuzzers always generate semantically valid test cases, but lack the targeting and tuning that Xsmith provides."
I look forward to reading more about how they do the targeting and tuning.
-
Web assembly book?
Binaryen or the LLVM of wasm: https://github.com/WebAssembly/binaryen
-
You can reduce web build file size by 4mb by using Binaryen
Download Binaryen
-
What's the best way to generate WASM programmatically?
Probably https://github.com/WebAssembly/binaryen/, there were various rust bindings to it.
-
Build a WebAssembly Language for Fun and Profit: Code Generation
The final phase of our compiler is code generation. This phase takes the AST and converts it to a set of executable instructions. In our case, WebAssembly. To accomplish this, we are going to use a popular WebAssembly compiler toolchain called binaryen.
-
Build a WebAssembly Language for Fun and Profit: Lexing
In this guide, we will be using TypeScript and NodeJS. The concepts are highly portable, so feel free to use the environment you're most comfortable with. Our only major dependency, binaryen, has a simple C API. You are welcome to skip ahead to the next section if you're using a different language.
-
Rust and WebAssembly without a Bundler
What are the size and performance benefits of processing the Wasm payload with wasm-opt?
-
Is WebAssembly Text (WAT) Just Another IR?
I would recommend looking into binaryen as it has it's own IR and can perform optimizations over it. It's also simpler than LLVM and has the option to produce binaries with debug names.
-
What are the advantages or disadvantages of compiling to VM Bytecode vs native machine code?
You can also use binaryen to optimize your wasm output
wasi-sdk
-
Stop Hiding the Sharp Knives: The WebAssembly Linux Interface
I would really love being able to take any POSIX command line tool, compile that to WASI, and run it on (at least) Linux, Windows and macOS like a regular executable without having to install a separate WASI runtime.
I'm a 'WASI convert' since I was able to take an ancient 8-bit assembler written in the mid-90's (http://xi6.com/projects/asmx/), compile that as-is with the WASI SDK (https://github.com/WebAssembly/wasi-sdk), and then integrate it into a VSCode extension (https://marketplace.visualstudio.com/items?itemName=floooh.v...).
A similar problem is I have is a shader cross-compiler (https://github.com/floooh/sokol-tools) which needs to run Linux, macOS and Windows and takes too long to build locally, thus I currently need to distribute that as pre-built binaries. Compiling this to WASI works, but the filesystem access restrictions built into current wasm runtimes are a hassle to manage, and it would require a WASI runtime to be separately installed).
-
WASI: WebAssembly System Interface
There is the WASI SDK if you want to target WASI from C/C++:
https://github.com/WebAssembly/wasi-sdk
It may not have all the amenities of Emscripten, but it's way less bulky.
-
How to Debug WASI Pipelines with ITK-Wasm
The most direct way to debug WebAssembly is through the WebAssembly System Interface (WASI). In itk-wasm, we can build to WASI with the WASI SDK by specifying the itkwasm/wasi toolchain image. A backtrace can quickly be obtained with the itk-wasm CLI. Or, a fully fledged debugger session can be started with LLDB.
-
Hello Wasm World!
We use the add_executable command to build executables with itk-wasm. The Emscripten and WASI toolchains along with itk-wasm build and execution configurations are contained in itk-wasm dockcross Docker images invoked by the itk-wasm command line interface (CLI). Note that the same code can also be built and tested with native operating system toolchains. This is useful for development and debugging.
-
Wasmer takes WebAssembly libraries mainstream with WAI
A more lightweight tool than emscripten is the WASI SDK (https://github.com/WebAssembly/wasi-sdk/releases). However, it doesn't generate JS or HTML.
-
A First Look at Wasm and Docker
wget https://github.com/WebAssembly/wasi-sdk/releases/download/wasi-sdk-16/wasi-sdk-16.0-macos.tar.gz
-
Turbocharge your application development using WebAssembly with SingleStoreDB
First, we’ll download the wasi-sdk. We’ll use wasi-sdk-16.0-linux.tar.gz, the latest version available when writing this article. We’ll move the file to the /opt directory and unpack it as follows:
-
whats all the fuzz about wasi-libc?
I'm intrigued. Pretty good write-up about it here. One would need an ebuild for wasi-libc and an ebuild for wasi-sdk.
-
Store SQLite in Cloudflare Durable Objects
The previously mentioned PR for wasm32-unknown-unknown compatibility solved this by including libc .c files from OpenBSD. My go to solution is different though. I prefer to build using the wasi-sdk (a WASI-enabled WebAssembly C/C++ toolchain).
-
WebAssembly and Back Again: Fine-Grained Sandboxing in Firefox 95
There's also the https://github.com/WebAssembly/wasi-sdk repo which is kind of a meta-build-system for all this.
But in FreeBSD we build all the pieces directly, here's our build recipes (with some hacks due to llvm's cmake code being stupid sometimes):
compiler-rt (from llvm): https://github.com/freebsd/freebsd-ports/blob/main/devel/was...
libc (from what you linked): https://github.com/freebsd/freebsd-ports/blob/main/devel/was...
libc++ (from llvm): https://github.com/freebsd/freebsd-ports/blob/main/devel/was...
What are some alternatives?
wasm-bindgen - Facilitating high-level interactions between Wasm modules and JavaScript
wasi-libc - WASI libc implementation for WebAssembly
linux - Linux kernel source tree
EasyOCR - Ready-to-use OCR with 80+ supported languages and all popular writing scripts including Latin, Chinese, Arabic, Devanagari, Cyrillic and etc.
asyncify - Standalone Asyncify helper for Binaryen
wasm-sqlite - [Experimental] SQLite compiled to WASM with pluggable page storage.
workers-wasi
nxdk - The cross-platform, open-source SDK to develop for original Xbox: *new* xdk
rusqlite - Ergonomic bindings to SQLite for Rust
One - One (onelang) is an open-source system programming language that makes it easy to build reliable, efficient and performant software. (release as soon) 1️⃣ 🕐 🩱