Hey everyone, to note for you: There's a dynamic check wther the CPU supports RDRAND and/or RDSEED before actually calling the asm code. I'll also include checks so that it'll fail if on the wrong architecture (-> not on x86 or x64)
I already saw something similar: The CPUID query code uses two distinct code paths, one for MSVC and one for GCC. It'd already help a lot if you could simply translate the code to MSVC style. (I'd do #if switches then) BR JPM Am Montag, 16. März 2015 13:17:40 UTC+1 schrieb Mouse: > > On Mar 16, 2015, at 5:37 , Ruben De Smet <[email protected] > <javascript:>> wrote: > > > Please do note that you have to have a CPU agnostic implementation too. > > People are running Crypto++ on Android, SPARC, etc. > > Yes, but don’t let that preclude one from having conditional CPU-specific > optimizations. You’re compiling a library for a specific CPU, after all. > > The code must run on many CPUs and platforms. But it would be silly not to > use, e.g., AES-NI and RDRAND when running on Intel, merely because SPARC > doesn’t have them. > > > -- -- 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.
