-
Notifications
You must be signed in to change notification settings - Fork 485
Closed
Description
The design repo says that memory operations serialize their offset immediate as a varuint32
, but the ml-proto binary-0xc branch uses varuint64
. I encounted this as the script-convert
branch of ml-proto converts this assert_invalid in address.wast is serializable, but invalid.
Should ml-proto use varuint32
for memory access offsets, or should the design repo be changed to use varuint64
?
And how should the script-convert branch handle this particular assert_invalid
if the offset were unserializable?
Metadata
Metadata
Assignees
Labels
No labels