You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WebAssembly names are essentially "sugar" over an index value.
S-Expressions are also "sugar"
There is a wabt tool called wat-desugar that can strip this stuff out.
I suspect that wasm-opcodecnt might also be useful when comparing approaches for similarity. Unique opcodes would likely distinguish approaches to problems.
Another approach might be to use wasm-opt passes from binaryen. However, this would likely complicate the code and make it less readable. This also is inherently lossy as it transforms the code for sake of efficiency. https://github.com/webassembly/binaryen
The text was updated successfully, but these errors were encountered:
Initial thoughts:
There is a wabt tool called
wat-desugar
that can strip this stuff out.I suspect that
wasm-opcodecnt
might also be useful when comparing approaches for similarity. Unique opcodes would likely distinguish approaches to problems.The
wassail
tool is also able to generate control flow graphs:https://github.com/acieroid/wassail
Another approach might be to use
wasm-opt
passes from binaryen. However, this would likely complicate the code and make it less readable. This also is inherently lossy as it transforms the code for sake of efficiency.https://github.com/webassembly/binaryen
The text was updated successfully, but these errors were encountered: