Stream: git-wasmtime

Topic: wasmtime / issue #1050 Make "wasm" and "compile" subcomma...

Wasmtime GitHub notifications bot (May 04 2022 at 20:16):

cfallin labeled issue #1050:

clif-util's "wasm" and "compile" subcommands essentially do the same thing, except that "wasm"'s input is a wasm file, and "compile"'s input is a clif file, but then they both do a full compilation. Currently, they print different things:

• "wasm" has a -v option which enables colorized messages like "Translating... ok", "compile" doesn't
• "compile" prints out the ".byte" sequence, "wasm" doesn't
• "compile" runs the capstone disassembler, "wasm" doesn't

and possibly other differences. We should harmonize these two subcommands.

Wasmtime GitHub notifications bot (Jan 17 2025 at 16:59):

erikrose commented on issue #1050:

clif-util's wasm subcommand was removed in 2be598bb456af13868a234f63698201a01775546, resolving any disharmony.

Wasmtime GitHub notifications bot (Jan 17 2025 at 17:07):

cfallin closed issue #1050:

clif-util's "wasm" and "compile" subcommands essentially do the same thing, except that "wasm"'s input is a wasm file, and "compile"'s input is a clif file, but then they both do a full compilation. Currently, they print different things:

• "wasm" has a -v option which enables colorized messages like "Translating... ok", "compile" doesn't
• "compile" prints out the ".byte" sequence, "wasm" doesn't
• "compile" runs the capstone disassembler, "wasm" doesn't

and possibly other differences. We should harmonize these two subcommands.

Last updated: Jan 24 2025 at 00:11 UTC