GT-multiexp: Add detailed metering - #541
Merged
Merged
Conversation
mratsim
force-pushed
the
meter-gt-multiexp
branch
from
April 3, 2025 01:25
1de90a3 to
a6c3d26
Compare
mratsim
force-pushed
the
meter-gt-multiexp
branch
from
April 3, 2025 01:26
a6c3d26 to
18d7ae8
Compare
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.
This is a followup to #485 with detailed function call counts and relative importance.
The data has been collated in a markdown file with detail number of Fp calls, mul/square on Fp2, and function calls on Fp12/GT/cyclotomic subgroup.
Due to ambiguity with generic functions, to ensure we can easily attribute contributions to the call stack: