Following the last blog called “Project: Part2 – Initial build testing on argon2 package using C and Assembler language(Progress 2)”
I will continue to blog about the build of argon2 password hashing function.
I will be testing using the following criteria(The crossed out are done in the Progress 2):
Check how many inline assembler code already exist Check how many dedicated/ separate assembler files exist in the package (File Extension: s or S) Check how many files use the C programming language (File Extension: c)
- Use a profiling tool to check how optimized the program is in the current build package (Tools such as: gprof, stap, etc.)
- Build the package and check the default results by testing the build against a password file. The file will be made using a Microsoft Excel formula.
- Check that the results are relatively consistent. (This will be from program compile time, program run time, and the program file size)
- Introduce a minor or major change that will optimize or reduce performance of the original program. This is done by changing the character(s) of the password file generated by the Microsoft Excel formula.
- Compare the results of the changes and the original program results.
Use a profiling tool to check how optimized the program is in the current build package (Tools such as: gprof, stap, etc.)
I will be using a profiling tool.