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.
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
Feat: Private input integration #622
Feat: Private input integration #622
Changes from all commits
aa59826
4ecc650
0c32eab
acccad7
8003c17
1090e5f
3b60782
44e227f
bc3c23c
25a193f
9a986a7
dc12d98
868f821
4d3d5be
b4ef853
b1fa9e8
c7cd4b5
4f15ceb
604dbc7
b0aab66
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On the discussion about private IO, someone suggested to use the term 'hint' throughout?
('Private input' works perfectly fine for me; but I remember some people having strong opinions on this.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I favor
hint
overprivate input
. Some places that use this terminology:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the ref. If the term "hint" is understood I’ll rename things to that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No worries, you can do that after you finish the sproll-evm test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#636
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we add a comment to say, if len(private_io) != len(private_input_file), then it is right-padded with 0s?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point. It is not padded. Or precisely it is zero-padded only to the next power-of-two size.
The rest of memory does not exist - unsatisfiable if the program tries to use it.
(added a comment and assert)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For technical reasons, if we are using rkyv, it would be better to pad from the left by default.
That's means the last byte that's specified should always appear in the same position in the VM.
That's good, and exactly what we want. Can you please make both the doc comment and the emulator reflect that behaviour?
Btw, would it be possible to make both kinds of padding be 'inaccessible' (from the point of view of the VM), instead of a mix of 0 and 'inaccessible'? That would be best!