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

export wasm memory #265

Merged
merged 1 commit into from
Jan 12, 2024
Merged

export wasm memory #265

merged 1 commit into from
Jan 12, 2024

Conversation

spoonincode
Copy link
Member

Exports the wasm memory.

Before,

wasm-objdump -j export -x eosio.token.wasm

eosio.token.wasm:	file format wasm 0x1

Section Details:

Export[1]:
 - func[56] <apply> -> "apply"

After,

wasm-objdump -j export -x eosio.token.wasm

eosio.token.wasm:	file format wasm 0x1

Section Details:

Export[2]:
 - memory[0] -> "memory"
 - func[24] <apply> -> "apply"

Resolves #130

@DenisCarriere
Copy link
Member

Tested, this works with Vert 👍

@spoonincode spoonincode merged commit b9e8265 into main Jan 12, 2024
6 checks passed
@spoonincode spoonincode deleted the export_wasm_memory branch January 12, 2024 21:08
@ericpassmore
Copy link
Contributor

Note:start
group: TOOLS
category: INTERNALS
summary: New feature to export memory from a wasm file.
Note: end

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

enable WASM memory exported to support Vert
4 participants