295cd8e60b
Try to add AppVeyor Cmake builds for debug and release
...
Take 26
2017-08-23 15:14:43 -04:00
94a9c6dc7b
Try to add AppVeyor Cmake builds for debug and release
...
Take 24
2017-08-23 15:11:29 -04:00
b15f7b7e34
Try to add AppVeyor Cmake builds for debug and release
...
Take 23
2017-08-23 14:56:41 -04:00
5c42f096f3
Try to add AppVeyor Cmake builds for debug and release
...
Take 21
2017-08-23 14:48:03 -04:00
4c9e59f4d2
Try to add AppVeyor Cmake builds for debug and release
...
Take 20
2017-08-23 14:27:42 -04:00
5fe020c6ff
Try to add AppVeyor Cmake builds for debug and release
...
Take 19
2017-08-23 13:48:52 -04:00
307fd35cba
Try to add AppVeyor Cmake builds for debug and release
...
Take 18
2017-08-23 13:30:57 -04:00
397f3ade13
Try to add AppVeyor Cmake builds for debug and release
...
Take 16
2017-08-23 13:27:12 -04:00
cf7fe07614
Try to add AppVeyor Cmake builds for debug and release
...
Take 15
2017-08-23 13:07:49 -04:00
a73ee56f33
Try to add AppVeyor Cmake builds for debug and release
...
Take 14
2017-08-23 13:05:13 -04:00
318af1e2a4
Try to add AppVeyor Cmake builds for debug and release
...
Take 13
2017-08-23 12:57:09 -04:00
cd40b7bcd8
Try to add AppVeyor Cmake builds for debug and release
...
Take 13
2017-08-23 12:35:18 -04:00
f021a9c627
Try to add AppVeyor Cmake builds for debug and release
...
Take 12
2017-08-23 12:22:41 -04:00
8e83dba05c
Try to add AppVeyor Cmake builds for debug and release
...
Take 11
2017-08-23 12:19:31 -04:00
dfa35595fb
Try to add AppVeyor Cmake builds for debug and release
...
Take 10
2017-08-23 12:00:47 -04:00
16a0cfeee1
Try to add AppVeyor Cmake builds for debug and release
...
Take 9
2017-08-23 11:55:47 -04:00
c9d3fbf165
Try to add AppVeyor Cmake builds for debug and release
...
Take 8
2017-08-23 11:50:57 -04:00
ab28f63015
Try to add AppVeyor Cmake builds for debug and release
...
Take 7
2017-08-23 11:44:38 -04:00
d079909ed5
Try to add AppVeyor Cmake builds for debug and release
...
Take 6
2017-08-23 11:43:52 -04:00
a73b1d50eb
Try to add AppVeyor Cmake builds for debug and release
...
Take 5
2017-08-23 11:37:56 -04:00
da00de7219
Try to add AppVeyor Cmake builds for debug and release
...
Take 3
2017-08-23 11:35:33 -04:00
5d2b8772b5
Try to add AppVeyor Cmake builds for debug and release
...
Take 2
2017-08-23 11:34:13 -04:00
0e899de2b2
Try to add AppVeyor Cmake builds for debug and release
2017-08-23 11:30:45 -04:00
8da7ed1abf
Try to fix AppVeyor CMake stub
...
Take 9
2017-08-23 09:37:28 -04:00
e4f806b281
Try to fix AppVeyor CMake stub
...
Take 8
2017-08-23 09:24:17 -04:00
24c8f8c3ed
Try to fix AppVeyor CMake stub
...
Take 7
2017-08-23 09:17:30 -04:00
798baf08d6
Try to fix AppVeyor CMake stub
...
Take 6
2017-08-23 09:13:04 -04:00
a261c4ff54
Try to fix AppVeyor CMake stub
...
Take 5
2017-08-23 09:07:55 -04:00
67807d1947
Try to fix AppVeyor CMake stub
...
Take 4
2017-08-23 09:01:40 -04:00
e6899c0e74
Try to fix AppVeyor CMake stub
...
Take 3
2017-08-23 08:49:52 -04:00
0b3032c5b3
Try to fix AppVeyor CMake stub
...
Take 2
2017-08-23 08:47:00 -04:00
db7af530b9
Try to fix AppVeyor CMake stub
2017-08-23 08:29:40 -04:00
0db29f5bdc
Update CMakeFileList.txt
2017-08-23 08:13:25 -04:00
e544ce3b9c
Fix missing neon-simd.o
2017-08-23 07:07:45 -04:00
7162f5c20e
Rename neon.cpp to neon-simd.cpp
...
More twiddling in CMakeList.txt
2017-08-23 06:41:27 -04:00
e1c99aea16
Test remove -march=native
...
Also see "Random crashes on different computers because option -march=native is active 'by default'", https://github.com/weidai11/cryptopp/issues/380
2017-08-23 05:10:03 -04:00
e0e8b63cee
Test remove -march=native
...
Also see "Random crashes on different computers because option -march=native is active 'by default'", https://github.com/weidai11/cryptopp/issues/380
2017-08-23 04:50:28 -04:00
4fef2951e3
Test remove -march=native
...
Also see "Random crashes on different computers because option -march=native is active 'by default'", https://github.com/weidai11/cryptopp/issues/380
2017-08-23 04:37:05 -04:00
a77ad75c1e
Test remove -march=native
...
Also see "Random crashes on different computers because option -march=native is active 'by default'", https://github.com/weidai11/cryptopp/issues/380
2017-08-23 02:36:18 -04:00
2b82aa9085
Test remove -march=native
...
Also see "Random crashes on different computers because option -march=native is active 'by default'", https://github.com/weidai11/cryptopp/issues/380
2017-08-23 02:34:37 -04:00
5c883d526a
Test remove -march=native
...
Also see "Random crashes on different computers because option -march=native is active 'by default'", https://github.com/weidai11/cryptopp/issues/380
2017-08-23 02:30:37 -04:00
66b431eb4b
Test remove -march=native
...
Also see "Random crashes on different computers because option -march=native is active 'by default'", https://github.com/weidai11/cryptopp/issues/380
2017-08-22 22:38:31 -04:00
e1c5fa9720
Test remove -march=native
...
Also see "Random crashes on different computers because option -march=native is active 'by default'", https://github.com/weidai11/cryptopp/issues/380
2017-08-22 22:34:55 -04:00
7b0b48af66
Test remove -march=native
...
Also see "Random crashes on different computers because option -march=native is active 'by default'", https://github.com/weidai11/cryptopp/issues/380
2017-08-22 22:00:02 -04:00
559fc3bd89
Fix benchmark selection code (GH #464 )
2017-08-22 05:10:25 -04:00
7851a0d510
Remove BOOL macro value (GH #462 )
...
Currently the CRYPTOPP_BOOL_XXX macros set the macro value to 0 or 1. If we remove setting the 0 value (the #else part of the expression), then the self tests speed up by about 0.3 seconds. I can't explain it, but I have observed it repeatedly.
This check-in prepares for the removal in Upstream master
2017-08-20 21:25:29 -04:00
bac3c1cc40
Fix Asan 64-bit build
...
The Padlock SDK sample code leaves a lot to be desired. Regariding the 64-bit samples and instr_linux64.asm... it looks like the sample sill uses 32-bit constants, but most anything related to extended registers, like rdi, is commented out
2017-08-20 11:19:32 -04:00
3db6f361d2
Fix compile under MSVC
...
(ClCompile target) ->
validat1.cpp(1081): warning C4800: 'CryptoPP::word32' : forcing value to bool
'true' or 'false' (performance warning) [c:\Users\cryptopp\cryptest.vcxproj]
validat1.cpp(1090): warning C4800: 'CryptoPP::word32' : forcing value to bool
'true' or 'false' (performance warning) [c:\Users\cryptopp\cryptest.vcxproj]
validat1.cpp(1099): warning C4800: 'CryptoPP::word32' : forcing value to bool
'true' or 'false' (performance warning) [c:\Users\cryptopp\cryptest.vcxproj]
2017-08-20 07:15:02 -04:00
40d0710d43
Fix compile under Clang
...
padlkrng.cpp:45:34: error: no matching function for call to 'STDMIN'
const size_t rem = STDMIN(ret, STDMIN(size, 16U));
^~~~~~
./misc.h:516:36: note: candidate template ignored: deduced conflicting types for parameter 'T' ('unsigned long' vs. 'unsigned int')
template <class T> inline const T& STDMIN(const T& a, const T& b)
^
1 error generated.
2017-08-20 07:09:10 -04:00
88f08afcb0
Add additional VIA RNG tests
...
The are configurations tests as recommended by Cryptography Research, Inc in their 2003 audit report
2017-08-20 07:01:59 -04:00
Jeffrey Walton