| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
kalyna.cpp:432: error: integer constant is too large for 'long' type
kalyna.cpp:509: error: integer constant is too large for 'long' type
kalyna.cpp:608: error: integer constant is too large for 'long' type
kalyna.cpp:713: error: integer constant is too large for 'long' type
kalyna.cpp:833: error: integer constant is too large for 'long' type
...
|
|
|
|
|
|
| |
globally scoped byte
This check-in supports Romain Geissler's work on cleaning up our use of ::byte when it collides with std::byte. Regardless of what happens, such as removing ::byte and adding CryptoPP::byte, providing the typedef here makes Kalyna immune to the outside changes. Also see Pull Request 437 and 438.
|
| |
|
| |
|
|
|
|
| |
Use Put and Get blocks consistently
|
|
|
|
| |
This reverts commit 76bb4ead40ded06b55b506a85106eae38519b7ee. The Visual Studio project files and other test files were not supposed to be checked-in.
|
|
|
|
| |
Use Put and Get blocks consistently
|
|
|
|
| |
word32"
|
| |
|
| |
|
|
|
|
| |
Tested on GCC110 from the GCC compile farm. Performance is comparable to AES on GCC110.
|
| |
|
|
|
|
| |
The code at check-in a5c67cfdd6ad7eeb did not include it. Unlike Threefish, it looks like Kalyna could benefit from the cache hardening given how similar Kalyna is to AES. The hardening costs less than 0.1 cpb, which equates to about 199 MB/s vs 201 MB/s on a 6th gen Skylake
|
|
Thanks to Roman Oliynykov and Oleksandr Kazymyrov for their assistance. Thanks to Keru Kuro for the reference implementation.
|