Updated benchmarks with arm-none-eabi-gcc 8.2.0 #23
Conversation
This file contains 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
|
It's surprising how NTRUprime remained constant throughout all of this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We've noticed some significant cycle count variations for different versions of gcc.
The previous benchmarks were unfortunately not all done using the same compiler version :(
I've redone all the benchmarks with the most recent arm-none-eabi-gcc (8.2.0) and toolchain on Arch. I do not expect any gcc updates soon - so these numbers should stay stable for a while.
I would welcome someone benchmarking this with an earlier gcc version.