-
Notifications
You must be signed in to change notification settings - Fork 615
feat(avm): storage #4673
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(avm): storage #4673
Changes from 46 commits
d630b44
518ec41
636c316
f92dcdd
c7986a3
ab832ff
5c5156f
aecdd3a
1002bb9
ec6ce1d
38181cd
9eeb153
ea0d0c6
9d4fe7e
e9db646
7af5de5
621f593
f2fe7fc
e92208f
1d26069
c4e0c5e
543e093
800a774
1bd7952
2522293
94466de
fdda301
d16dd58
eded899
025dc2a
d633b8b
3a327dd
a932153
7525ee8
4997ce4
1ad0307
d534d2d
85d7ce8
1bde64b
ccd689f
4916061
b90675d
84670d6
332f333
957d0bd
d0386d4
51f8570
3499714
78de9b7
6cdd047
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| [package] | ||
| name = "should_fail_with_mismatch" | ||
| type = "bin" | ||
| authors = [""] | ||
| [dependencies] |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,6 @@ | ||
| import { strict as assert } from 'assert'; | ||
|
|
||
| import { TaggedMemory, TypeTag } from '../avm_memory_types.js'; | ||
| import { TaggedMemory } from '../avm_memory_types.js'; | ||
|
|
||
| export enum AddressingMode { | ||
| DIRECT, | ||
|
|
@@ -51,7 +51,8 @@ export class Addressing { | |
| for (const [i, offset] of offsets.entries()) { | ||
| switch (this.modePerOperand[i]) { | ||
| case AddressingMode.INDIRECT: | ||
| mem.checkTag(TypeTag.UINT32, offset); | ||
| // NOTE(reviewer): less than equal is a deviation from the spec - i dont see why this shouldnt be possible! | ||
| mem.checkIsValidMemoryOffsetTag(offset); | ||
| resolved[i] = Number(mem.get(offset).toBigInt()); | ||
|
Comment on lines
53
to
56
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🤔 we shouldn't have to do this since AVM memory offsets are all supposed to be 32 bits
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is a consequence of the comment above, the address space of brillig / ssa were misaligned, as long as no one is trying to use the avm this week, I can wait for that to be resolved and just stack on this pr |
||
| break; | ||
| case AddressingMode.DIRECT: | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.