feat(deap): address space mapping #809
Merged
Conversation
This file contains hidden or 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
th4s
approved these changes
Apr 24, 2025
|
Ouch, just remembered we assume contiguous memory allocations in the |
sinui0
force-pushed
the
refactor/deap-memory
branch
from
8f5ee7b to
0eb1158
Compare
th4s
force-pushed
the
feat/prf-local
branch
2 times, most recently
from
0a371e9 to
78a51b1
Compare
sinui0
force-pushed
the
refactor/deap-memory
branch
3 times, most recently
from
65c68cd to
d047851
Compare
sinui0
force-pushed
the
refactor/deap-memory
branch
from
d047851 to
08fd128
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR adds address space mapping to DEAP so that the MPC and ZK memories do not have to be synchronized. This allows us to dynamically allocate freely.