> I think the options are: > > (1) Remove RDSEED completely until GCC provides full support > (2) Disable RDSEED for the Unix on Windows gear until GCC provides full > support > (3) Provide an ASM implementation that always "just works" > > What is the course of action we should take? > > My "vote": > > I'd vote for (3) if we can't make the intrinsics work. This will also > enable us to provide RDSEED ( / RDRAND) for older compiler versions (pre- > 4.6 and pre- 4.8) > > If this is too much work, (2) may be an option. > > We should avoid (1) if anyhow possible. >
Yes, agreed. I like it when things "just work" :) We can (1) provide the ASM that always "just works" and (2) provide an optional Intrinsics in case things go sideways in unexpected ways. Jeff -- -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com. 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 cryptopp-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
