Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[submission] wabt: initial port for the Web Assembly Binary Toolkit #27528

Merged
merged 1 commit into from
Jan 28, 2025

Conversation

easye
Copy link
Contributor

@easye easye commented Jan 28, 2025

A collection of utilities for working with webassembly ("wasm") binaries.

From https://github.com/WebAssembly/wabt:

 WABT (we pronounce it "wabbit") is a suite of tools for WebAssembly, including:

     wat2wasm: translate from WebAssembly text format to the WebAssembly binary format
     wasm2wat: the inverse of wat2wasm, translate from the binary
       format back to the text format (also known as a .wat)
     wasm-objdump: print information about a wasm binary. Similiar to objdump.
     wasm-interp: decode and run a WebAssembly binary file using a stack-based interpreter
     wasm-decompile: decompile a wasm binary into readable C-like syntax.
     wat-desugar: parse .wat text form as supported by the spec
       interpreter (s-expressions, flat syntax, or mixed) and print
       "canonical" flat format
     wasm2c: convert a WebAssembly binary file to a C source and header
     wasm-strip: remove sections of a WebAssembly binary file
     wasm-validate: validate a file in the WebAssembly binary format
     wast2json: convert a file in the wasm spec test format to a JSON file
      and associated wasm binary files
     wasm-stats: output stats for a module
     spectest-interp: read a Spectest JSON file, and run its tests in the interpreter

 These tools are intended for use in (or for development of) toolchains
 or other systems that want to manipulate WebAssembly files. Unlike the
 WebAssembly spec interpreter (which is written to be as simple,
 declarative and "speccy" as possible), they are written in C/C++ and
 designed for easier integration into other systems. Unlike Binaryen
 these tools do not aim to provide an optimization platform or a
 higher-level compiler target; instead they aim for full fidelity and
 compliance with the spec (e.g. 1:1 round-trips with no changes to
 instructions).

A collection of utilities for working with webassembly ("wasm")
binaries.

From <https://github.com/WebAssembly/wabt>:

     WABT (we pronounce it "wabbit") is a suite of tools for WebAssembly, including:

         wat2wasm: translate from WebAssembly text format to the WebAssembly binary format
         wasm2wat: the inverse of wat2wasm, translate from the binary
           format back to the text format (also known as a .wat)
         wasm-objdump: print information about a wasm binary. Similiar to objdump.
         wasm-interp: decode and run a WebAssembly binary file using a stack-based interpreter
         wasm-decompile: decompile a wasm binary into readable C-like syntax.
         wat-desugar: parse .wat text form as supported by the spec
           interpreter (s-expressions, flat syntax, or mixed) and print
           "canonical" flat format
         wasm2c: convert a WebAssembly binary file to a C source and header
         wasm-strip: remove sections of a WebAssembly binary file
         wasm-validate: validate a file in the WebAssembly binary format
         wast2json: convert a file in the wasm spec test format to a JSON file
          and associated wasm binary files
         wasm-stats: output stats for a module
         spectest-interp: read a Spectest JSON file, and run its tests in the interpreter

     These tools are intended for use in (or for development of) toolchains
     or other systems that want to manipulate WebAssembly files. Unlike the
     WebAssembly spec interpreter (which is written to be as simple,
     declarative and "speccy" as possible), they are written in C/C++ and
     designed for easier integration into other systems. Unlike Binaryen
     these tools do not aim to provide an optimization platform or a
     higher-level compiler target; instead they aim for full fidelity and
     compliance with the spec (e.g. 1:1 round-trips with no changes to
     instructions).
@macportsbot macportsbot added type: submission by: member Created by a member with commit rights labels Jan 28, 2025
@easye easye merged commit 95aceb9 into macports:master Jan 28, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
by: member Created by a member with commit rights type: submission
Development

Successfully merging this pull request may close these issues.

2 participants