This repository has been archived by the owner on Dec 27, 2023. It is now read-only.
experimental wnaf type change + try flatten MultiExp input #32
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 is experimental, just for illustration, it needs review, and maybe some of the changes are worthwhile.
The wnaf type:
int
as element type, even though for the default window size, it could fit in aint8
, a 8x size reductionint8
, but that's fine.And
MultiExp
has a[]*PointG1
input, while I much prefer[]PointG1
, since we allocate large arrays of these, and there is no use for an unnecessary extra layer of indirection. Or maybe an alternative function could be exposed, with this input type?Benchmark: