Timing benchmark #520

Open
sjaeckel wants to merge 5 commits from timing-benchmark into develop
sjaeckel commented 2019-11-07 12:03:26 -06:00 (Migrated from github.com)

This modifies how the timing demo of RSA and ECC work.

  1. it updates the timing output to be easier machine-readable.
  2. it introduces reference-keys to measure the timing.
This modifies how the timing demo of RSA and ECC work. 1. it updates the timing output to be easier machine-readable. 1. it introduces reference-keys to measure the timing.
karel-m (Migrated from github.com) requested changes 2021-04-09 10:01:03 -05:00
karel-m (Migrated from github.com) left a comment

Could you please move changes related to src/math/ltm_desc.c into a separate PR?

The rest is IMO fine for merging.

Could you please move changes related to `src/math/ltm_desc.c` into a separate PR? The rest is IMO fine for merging.
karel-m (Migrated from github.com) approved these changes 2021-04-15 12:40:28 -05:00
This pull request has changes conflicting with the target branch.
  • appveyor.yml
  • demos/timing.c
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin 'timing-benchmark:timing-benchmark'
git switch 'timing-benchmark'

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch 'develop'
git merge --no-ff 'timing-benchmark'
git switch 'timing-benchmark'
git rebase 'develop'
git switch 'develop'
git merge --ff-only 'timing-benchmark'
git switch 'timing-benchmark'
git rebase 'develop'
git switch 'develop'
git merge --no-ff 'timing-benchmark'
git switch 'develop'
git merge --squash 'timing-benchmark'
git switch 'develop'
git merge --ff-only 'timing-benchmark'
git switch 'develop'
git merge 'timing-benchmark'
git push origin 'develop'
Sign in to join this conversation.
No reviewers
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
gh-libtom/libtomcrypt!520
No description provided.