-
Notifications
You must be signed in to change notification settings - Fork 7
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
General purpose instructions for bytes #49
Comments
kwannoel
added a commit
that referenced
this issue
Jul 6, 2021
Includes methods from Batch 2. See: #49
kwannoel
added a commit
that referenced
this issue
Jul 7, 2021
Includes methods from Batch 2. See: #49
kwannoel
added a commit
that referenced
this issue
Jul 9, 2021
Includes methods from Batch 2. See: #49
kwannoel
changed the title
Implement EVM type descriptors
General purpose instructions for bytes
Jul 9, 2021
kwannoel
added a commit
that referenced
this issue
Jul 9, 2021
kwannoel
added a commit
that referenced
this issue
Jul 9, 2021
kwannoel
added a commit
that referenced
this issue
Jul 9, 2021
kwannoel
added a commit
that referenced
this issue
Jul 9, 2021
kwannoel
added a commit
that referenced
this issue
Jul 21, 2021
kwannoel
added a commit
that referenced
this issue
Jul 21, 2021
kwannoel
added a commit
that referenced
this issue
Jul 21, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Part of https://gitlab.com/mukn/glow/-/issues/80.
Features
Batch 1 (Merged: #46)
Batch 2 (WIP: #50)
mstoreat
,mloadat
.For example, given a
Bytestring
with aUInt64
length,during compile time we do not know the actual length / contents of the bytestring.
instead we generate instructions to store the length:
- on stack is just takes up a slot.
- in memory it takes up 8bytes.
And use it to decode the contents:
- LOAD:
Use the offset and length on stack to retrieve the entire bytestring from memory
- STORE:
Use length on stack to store bytestring in memory
Batch 3
.evm<-
method for marshalling data to EVM.Batch 4
The text was updated successfully, but these errors were encountered: