Reduce number of PoT checkpoints 2x #1708
Merged
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.
Since we have unusual use of AES, we don't really care whether we're doing encoding or decoding, we have both inputs and outputs either way.
If that is the case, why don't we cut number of checkpoints in half and for every sub-interval (between two checkpoints) do this instead:
Essentially run half of iterations in forward and half of iterations in backward direction, then compare that both resulted in the same middle value.
This way with 8 checkpoints instead of 16 we still get the same instruction-level parallelism and the same verification performance (as I have confirmed with benchmarks).
Code contributor checklist: