-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
fix: Validate Circular Buffer Capacity #91
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
b42dac9
fix: Validate Circular Buffer Capacity
bushidocodes 46ceb46
fix: cap memory in proof
bushidocodes d11433b
refactor: Remove suspicious power of 2 number
bushidocodes 6bd4db7
Update exercises/practice/circular-buffer/.meta/proof.ci.wat
bushidocodes fc719e2
feat: Circular Buffer can grow up to four pages
bushidocodes 60e16a2
Update exercises/practice/circular-buffer/circular-buffer.wat
bushidocodes e425c53
docs: Enhance hints for Circular Buffer
bushidocodes 79b8f7d
docs: Update linear memory comment in proof.ci.wat for circular buffer
bushidocodes File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,16 @@ | ||
# Hints | ||
|
||
Linear memory is byte-addressable, but `i32` has a width of four bytes. | ||
`i32` has a width of four bytes. | ||
|
||
"A memory instance... holds a vector of bytes. The length of the vector always is a multiple of the WebAssembly page size, which is defined to be the constant 65536" | ||
|
||
[WebAssembly Specification: Memory Instances](https://webassembly.github.io/spec/core/exec/runtime.html#page-size) | ||
|
||
"The `memory.size` instruction returns the current size of a memory. The `memory.grow` instruction grows memory by a given delta and returns the previous size, or -1 if enough memory cannot be allocated. Both instructions operate in units of page size." | ||
|
||
[WebAssembly Specification: Memory Instructions](https://webassembly.github.io/spec/core/syntax/instructions.html#syntax-instr-memory) | ||
|
||
Further References: | ||
|
||
- [memory.size at MDN](https://developer.mozilla.org/en-US/docs/WebAssembly/Reference/Memory/Size) | ||
- [memory.grow at MDN](https://developer.mozilla.org/en-US/docs/WebAssembly/Reference/Memory/Grow) |
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
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
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
Oops, something went wrong.
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.
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.
Do you want
(newCap - 1) / 16384
or(newCap / 16384) - 1
here? I think the latter.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.
The latter actually ends up allocating too few pages I believe due to integer division acting like a floor:
x idiv y ~= floor(x/y)
i.e. when we want to allocate a circular buffer that holds one more than we can fit in 1 page.
(newCap - 1) / 16384
((16385 - 1) idiv 16384) => (16384 idiv 16384) => 1
(newCap / 16384) - 1
((16385 idiv 16384) - 1) => (1 - 1) => 0
I checked this by modifying the solution to
(memory.grow (i32.sub (i32.div_s (local.get $newCapacity) (i32.const 16384)) (i32.const 1)))
and got the following: