Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Fix use of <x86intrin.h> for MSVC (GH #1198) | Jeffrey Walton | 2023-04-15 | 1 | -2/+4 |
| | | | | It seems Microsoft now defines GCC defines, like __BMI__ | ||||
* | Use std namespace for memset, memcpy, memcmp (#1204) | Jeffrey Walton | 2023-04-15 | 1 | -6/+6 |
| | |||||
* | Cleanup after merging PR #1043 | Jeffrey Walton | 2022-02-14 | 1 | -43/+2 |
| | |||||
* | Fix issue with VS runtime checks for data truncation (#1043) | ejl103 | 2022-02-14 | 1 | -2/+44 |
| | | | | | | | | | When running VS with the 'c' runtime check on for data truncation (see https://docs.microsoft.com/en-us/cpp/build/reference/rtc-run-time-error-checks?view=msvc-160) This code will throw errors because the 64 bit ptr gets truncated to a 32bit value. Normally I'd disable this using the pragma specifically for this code, but sadly that doesn't work for template functions, so I have come up with a way to get the appropriate masking type for any template combinations and using the recommended way to silence the error without impacting the quality of the generated code. This code could be more concise in modern C++ but it seems the project expects to support C++03 so this should work fine there. All tests passed locally for me on Windows (some asserts but verified they were the same before my changes) | ||||
* | Clear unused variable warnings | Jeffrey Walton | 2022-01-13 | 1 | -2/+6 |
| | |||||
* | Add word128 overloads to misc.h | Jeffrey Walton | 2022-01-13 | 1 | -1/+154 |
| | |||||
* | Update documentation | Jeffrey Walton | 2022-01-13 | 1 | -5/+71 |
| | |||||
* | Add ByteReverse(word128 value) | Jeffrey Walton | 2022-01-12 | 1 | -0/+13 |
| | | | | This speeds up XTS mode on x86_64 by 0.11 cpb | ||||
* | Update documentation | Jeffrey Walton | 2021-03-10 | 1 | -6/+6 |
| | |||||
* | Fix spelling | Jeffrey Walton | 2021-03-10 | 1 | -23/+32 |
| | |||||
* | Add EnumToInt conversion macro for enum-enum conversion warnings (GH #1016) | Jeffrey Walton | 2021-03-09 | 1 | -0/+11 |
| | |||||
* | Revert e235ac57e85b (GH #992) | Jeffrey Walton | 2020-12-28 | 1 | -4/+3 |
| | | | | These damn aligned arrays are going to be the death of us... | ||||
* | Use pointer-to-T in IsAligned<T> (GH #992) | Jeffrey Walton | 2020-12-28 | 1 | -3/+4 |
| | |||||
* | Update documentation | Jeffrey Walton | 2020-12-25 | 1 | -2/+2 |
| | |||||
* | Update documentation | Jeffrey Walton | 2020-12-25 | 1 | -2/+2 |
| | |||||
* | Update documentation | Jeffrey Walton | 2020-12-25 | 1 | -6/+5 |
| | |||||
* | Use \return and \throw consitently in the docs | Jeffrey Walton | 2020-12-07 | 1 | -42/+42 |
| | |||||
* | Fix Clang version numbers for memset_z | Jeffrey Walton | 2020-09-15 | 1 | -2/+2 |
| | |||||
* | Update documentation (GH #966) | Jeffrey Walton | 2020-09-15 | 1 | -8/+11 |
| | |||||
* | Use define CRYPTOPP_CXX11_STATIC_INIT name | Jeffrey Walton | 2020-08-07 | 1 | -1/+1 |
| | |||||
* | Remove __BIGGEST_ALIGNMENT__ from GetAlignmentOf | Jeffrey Walton | 2020-08-06 | 1 | -5/+0 |
| | |||||
* | Use CRYPTOPP_CXX11_ATOMIC define | Jeffrey Walton | 2020-08-06 | 1 | -2/+2 |
| | |||||
* | Fix define CRYPTOPP_CXX17_STATIC_ASSERT name | Jeffrey Walton | 2020-08-05 | 1 | -1/+1 |
| | | | | That's a C++17 feature, not C++11 | ||||
* | Fix spelling | Jeffrey Walton | 2020-07-07 | 1 | -2/+2 |
| | |||||
* | Whitespace check-in | Jeffrey Walton | 2020-05-11 | 1 | -227/+227 |
| | |||||
* | Clean GCC 10 Analyzer warnings | Jeffrey Walton | 2020-05-11 | 1 | -6/+6 |
| | |||||
* | Clean GCC 10 Analyzer warnings | Jeffrey Walton | 2020-05-10 | 1 | -1/+2 |
| | |||||
* | Clean GCC 10 Analyzer warnings | Jeffrey Walton | 2020-05-10 | 1 | -1/+2 |
| | |||||
* | Clear signed/unsigned warnings under Clang | Jeffrey Walton | 2019-10-05 | 1 | -22/+22 |
| | |||||
* | Don't add semicolon to CRYPTOPP_CONSTANT abd DOCUMENTED_TYPEDEF (GH #889) | Jeffrey Walton | 2019-10-03 | 1 | -16/+16 |
| | | | | This issue is a recurring issue. Let's try fixing it in the #define this time. | ||||
* | Add BytePtr and ConstBytePtr overloads for SecByteBlock (GH #890) | Jeffrey Walton | 2019-10-03 | 1 | -2/+25 |
| | |||||
* | Avoid circular dependency using AlignedAllocate (GH #885) | Jeffrey Walton | 2019-09-28 | 1 | -56/+4 |
| | |||||
* | Whitespace check-in | Jeffrey Walton | 2019-07-27 | 1 | -1/+1 |
| | |||||
* | Fix macro paste in CRYPTOPP_ASSERT_JOIN | Jeffrey Walton | 2019-07-14 | 1 | -5/+3 |
| | |||||
* | Fix macro paste in CRYPTOPP_ASSERT_JOIN | Jeffrey Walton | 2019-07-14 | 1 | -2/+3 |
| | |||||
* | CRYPTOPP_CXX11_STATIC_ASSERT -> CRYPTOPP_CXX14_STATIC_ASSERT | Jeffrey Walton | 2019-07-14 | 1 | -1/+1 |
| | | | | WHoops, this is a C++14 feature | ||||
* | Use C++ static_assert from N3928 when available | Jeffrey Walton | 2019-07-14 | 1 | -12/+19 |
| | |||||
* | Update documentation | Jeffrey Walton | 2019-07-14 | 1 | -8/+10 |
| | |||||
* | Avoid preprocessor error in SIZE_MAX (GH #864) | Jeffrey Walton | 2019-07-14 | 1 | -2/+2 |
| | |||||
* | Update documentation | Jeffrey Walton | 2019-07-06 | 1 | -5/+6 |
| | |||||
* | Use CRYPTOPP_CXX11_DELETED_FUNCTIONS in NotCopyable | Jeffrey Walton | 2019-07-01 | 1 | -4/+9 |
| | |||||
* | Avoid ARM rev on Aarch64 | Jeffrey Walton | 2019-06-04 | 1 | -20/+16 |
| | | | | This broke Aarch64 | ||||
* | Fix compile on iOS | Jeffrey Walton | 2019-06-01 | 1 | -2/+4 |
| | |||||
* | Fix OS X compile with Clang later than 6.0 | Jeffrey Walton | 2019-05-31 | 1 | -5/+14 |
| | | | | It looks like Apple Clang 6.0 does not provide _blsr_u32 and friends. Later versions of Clang defines _blsr_u32 and it causes a stream of warnings. | ||||
* | Fix OS X compile with Clang 6.0 | Jeffrey Walton | 2019-05-31 | 1 | -0/+9 |
| | |||||
* | Add 16-bit rev16 and rbit | Jeffrey Walton | 2019-05-28 | 1 | -3/+11 |
| | |||||
* | Use ARM rev and rbit when appropriate | Jeffrey Walton | 2019-05-27 | 1 | -11/+41 |
| | | | | We tried to add a ByteReverse(word64) and BitReverse(word64) overloads but GCC was producing bad code for it. | ||||
* | Clear Valgrind finding in IncrementCounterByOne | Jeffrey Walton | 2019-05-25 | 1 | -6/+18 |
| | | | | The single buffer IncrementCounterByOne generated a Valgrind finding on ARM. This commit uses the same pattern for both overloads in case Valgrind wants to fire on the two-buffer version. | ||||
* | Fix IncrementCounterByOne | Jeffrey Walton | 2019-05-25 | 1 | -3/+0 |
| | | | | This was introduced earlier in the day when clearing a Valgrind finding. It tested good with the self tests. However, we double process byte[0] if there's a carry. | ||||
* | Clear Valgrind warnings on ARM | Jeffrey Walton | 2019-05-25 | 1 | -3/+10 |
| | | | | I don't believe these should have been findings. They were clear on x86, Aarch64 and PowerPC. |