converted registers to relocatable cells and bug fixes #66
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.
converted registers to relocatable cells and bug fixes
Time spent on this PR: 2 hours
Pull request type
Please check the type of change your PR introduces:
What is the current behavior?
Currently, registers are seen as felts which poses problem to relocate (since we need to add a +1 offset to all addresses for relocatables).
What is the new behavior?
Now all registers are considered as relocatables (=cells in google sheets).
This implied to change certain formulas for addition in GS (hence the enhancement of the segment element addition functions which are also now more reliable as they can work with columns like "AA" and cells like "Program!AD32").
The VM works fine with signed integers everywhere except for builtins for which the output is different depending on wether the inputs are signed or not. So builtin inputs are internally converted to unsigned ints (as felts would be >0 and <PRIME) and the ouputs are converted to signed ints since the rest of the VM works with signed ints. Like so assert_eqs between instructions and builtin outputs don't fail.