Am Freitag, 15. April 2016 07:43:02 UTC+2 schrieb Jeffrey Walton: > > I want to check if there's any opposition to SSE4.1 and SSE4.2 feature > detection. We can use it for modern algorithms on occasion, like BLAKE2. > > I don't plan on hand-coded SSE4.2 ASM, so I'm limiting it to intrinsics at > this point. We can put it to immediate use with the upcoming BLAKE2. >
Could that also be used to guard _mm_insert_epi32 (SSE4.1)? Its usage in rijndael.cpp is already guarded by CRYPTOPP_BOOL_AESNI_INTRINSICS_AVAILABLE and HasAESNI() and I don't know about any CPU that supports AESNI but doesn't support SSE4.1, but I've recently seen some crash dumps because of an invalid instruction exception in that code (on Windows with Visual Studio 2013). Marcel -- -- 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.
