wasm-micro-runtime/test-tools/aot-analyzer
YAMAMOTO Takashi 95edef3185
Bump AOT_CURRENT_VERSION for WAMR 2.x (gc, memory64) (#3880)
* Bump AOT_CURRENT_VERSION for WAMR 2.x (gc, memory64)

Maybe it's too late because we have already made a few releases
since then.
But this might still help users who haven't upgraded to WAMR 2.x yet.
Also, for the purpose of the versioning, it's safer to bump
needlessly than missing necessary bumps.

Fixes https://github.com/bytecodealliance/wasm-micro-runtime/issues/3837

* test-tools/aot-analyzer/include/config.h: bump AOT_CURRENT_VERSION
2024-10-29 11:26:06 +08:00
..
include Bump AOT_CURRENT_VERSION for WAMR 2.x (gc, memory64) (#3880) 2024-10-29 11:26:06 +08:00
src aot-analyzer: Fix a few printf formats (#3590) 2024-07-02 15:32:38 +08:00
CMakeLists.txt aot-analyzer: Fix macos build (#3589) 2024-07-02 15:25:03 +08:00
README.md Add aot binary analysis tool aot-analyzer (#3379) 2024-05-08 16:31:39 +08:00

AoT-Analyzer: The AoT Binary analysis tool

Cloning

Clone as normal:

$ git clone 
$ cd aot-analyzer

Building using CMake directly

You'll need CMake. You can then run CMake, the normal way:

$ mkdir build
$ cd build
$ cmake ..
$ cmake --build .

To analyze AoT files with GC feature enabled, you need to enable GC feature when compiling this tool:

$ mkdir build
$ cd build
$ cmake -DWAMR_BUILD_GC=1 ..
$ cmake --build .

Running aot-analyzer

Some examples:

# parse example.aot, and print basic information about AoT file
$ ./aot-analyzer -i example.aot

# parse example.aot, and print the size of text section of the AoT file
$ ./aot-analyzer -t example.aot

# compare these two files, and show the difference in function size between them
$ ./aot-analyzer -c example.aot example.wasm

NOTE: Using -c for file comparison, must ensure that the AoT file is generated based on this Wasm file.

You can use --help to get additional help:

$ ./aot-analyzer --help