gt-multiexp: meter lazy reduction primitive#543
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
In #541 I forgot to meter the FpDbl primitives used in lazy reduction as described in:
Efficient Implementation of Bilinear Pairings on ARM Processors
Gurleen Grewal, Reza Azarderakhsh,
Patrick Longa, Shi Hu, and David Jao, 2012
https://eprint.iacr.org/2012/408.pdf
The Realm of the Pairings
Diego F. Aranha and Paulo S. L. M. Barreto
and Patrick Longa and Jefferson E. Ricardini, 2013
https://eprint.iacr.org/2013/722.pdf
http://sac2013.irmacs.sfu.ca/slides/s1.pdf
Note that this significantly increased benchmarking overhead and the timings between torus/non-torus are not indicative of the real timing differences. See for example the change in timins at the GT level for Fp12 over Fp4 towering