mirror of
https://github.com/bytecodealliance/wasm-micro-runtime.git
synced 2025-02-06 06:55:07 +00:00
8239dd4aa7
Support to get `wasm_memory_type_t memory_type` from API `wasm_runtime_get_import_type` and `wasm_runtime_get_export_type`, and then get shared flag, initial page cout, maximum page count from the memory_type: ```C bool wasm_memory_type_get_shared(const wasm_memory_type_t memory_type); uint32_t wasm_memory_type_get_init_page_count(const wasm_memory_type_t memory_type); uint32_t wasm_memory_type_get_max_page_count(const wasm_memory_type_t memory_type); ``` |
||
---|---|---|
.. | ||
include | ||
src | ||
CMakeLists.txt | ||
README.md |
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