You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 5, 2025. It is now read-only.
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
This is a big patch involving several entries that cleans up the PHS declarations, defines limits for the input parameters, and provides a mechanism for automatically generating test vectors for each of them other than PolyPassHash, which generates different results each time it's PHS function is called.
I wish to use this for automated benchmarking, among other things. It is not required that these changes be pulled upstream, but it will allow you to compile and test the various entries through a common interface. I tried to keep the actual code changes to the entries minimal. For example, I have not fixed compiler warnings. The entries are built with a new Makefile, using common compiler flags, and supports opt (the default) and debug targets.
Thanks Bill! I'll let PHK approve or challenge your pr.
On Apr 14, 2014 6:16 PM, "Bill" [email protected] wrote:
This is a big patch involving several entries that cleans up the PHS
declarations, defines limits for the input parameters, and provides a
mechanism for automatically generating test vectors for each of them other
than PolyPassHash, which generates different results each time it's PHS
function is called.
I wish to use this for automated benchmarking, among other things. It is
not required that these changes be pulled upstream, but it will allow you
to compile and test the various entries through a common interface. I tried
to keep the actual code changes to the entries minimal. For example, I have
not fixed compiler warnings. The entries are built with a new Makefile,
using common compiler flags, and supports opt (the default) and debug
targets.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
None yet
3 participants
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 big patch involving several entries that cleans up the PHS declarations, defines limits for the input parameters, and provides a mechanism for automatically generating test vectors for each of them other than PolyPassHash, which generates different results each time it's PHS function is called.
I wish to use this for automated benchmarking, among other things. It is not required that these changes be pulled upstream, but it will allow you to compile and test the various entries through a common interface. I tried to keep the actual code changes to the entries minimal. For example, I have not fixed compiler warnings. The entries are built with a new Makefile, using common compiler flags, and supports opt (the default) and debug targets.
Bill