Support table64 extension in classic-interp and AOT running mode #3811
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ic-interp and aot pass the memory64 spec test now
wenyongh
reviewed
Oct 8, 2024
TianlongLiang
requested review from
loganek,
lum1n0us,
no1wudi,
xujuntwt95329 and
yamt
as code owners
lum1n0us
reviewed
Oct 9, 2024
lum1n0us
reviewed
Oct 9, 2024
lum1n0us
reviewed
Oct 9, 2024
lum1n0us
reviewed
Oct 9, 2024
lum1n0us
reviewed
Oct 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add table64 extension(in Memory64 proposal) support in classic-interp and AOT running mode, currently still use uint32 to represent table's init and max size to keep AOT ABI unchanged.