On Tue, Sep 13, 2016 at 10:17 AM, Andrew Marlow <[email protected]> wrote: > On Tuesday, 13 September 2016 12:04:35 UTC+1, Jeffrey Walton wrote: >> >> [snip] >> > This did not resolve the problem. >> >> That's a _really_ bad sign. We are quickly approaching the "compiler >> bug" wall since you just tried to use a straight C/C++ implementation. > > > Looks that way. :-(
Ok, I went through my lab book and I see some notes that may apply from a few years ago... let's try one more thing... Open sha.h and find the template definitions for SHA384 and SHA512. The last expression is "(CRYPTOPP_BOOL_X86|CRYPTOPP_BOOL_X32)". That's a template argument that controls 16-byte aligned/unaligned. Change it to "true". That should cause OptimalDataAlignment() to always return 16. In the mean time, I'll look through sha.cpp looking for potential suspects. 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.
