On Tuesday, September 22, 2015 at 9:48:32 AM UTC-4, [email protected] wrote: > > > > Am Montag, 21. September 2015 23:14:34 UTC+2 schrieb Jeffrey Walton: >> >> We pushed a cryptopp563rc4.zip at >> https://sourceforge.net/projects/cryptopp/files/cryptopp/5.6.3/ >> <https://www.google.com/url?q=https%3A%2F%2Fsourceforge.net%2Fprojects%2Fcryptopp%2Ffiles%2Fcryptopp%2F5.6.3%2F&sa=D&sntz=1&usg=AFQjCNEpdHXIdQCCTWUTd3HEoce-xLiJDQ>, >> >> but we have not yet announced it. >> > > Unfortunately there are a lot of compile errors now with MSVC x64 because > of changes to config.h. In the version on GitHub and in RC1, the definition > of CRYPTOPP_BOOL_SSE2_ASM_AVAILABLE was inside a preprocessor block that > excluded MSVC x64. Now both CRYPTOPP_BOOL_SSE2_ASM_AVAILABLE and > CRYPTOPP_X64_MASM_AVAILABLE are defined, leading to two "case 1:" in > GCM_Base::AuthenticateBlocks, for example. Also, CRYPTOPP_X64_ASM_AVAILABLE > is now wrongly defined for MSVC, which doesn't support x64 inline assembly. > > Adding "&& (!defined(_MSC_VER) || CRYPTOPP_BOOL_X86)" to the condition for > CRYPTOPP_BOOL_SSE2_ASM_AVAILABLE and adding "&& !defined(_MSC_VER)" to the > condition for CRYPTOPP_X64_ASM_AVAILABLE fixes these errors for me. > > Additionally, there is a compile error because x64 inline assembly is now > used in sha.cpp. This is because a CRYPTOPP_GENERATE_X64_MASM was changed > to CRYPTOPP_X64_MASM_AVAILABLE in this file. >
Thanks Am. I'll get on those shortly. Jeff -- -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com. --- You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
