Hi Everyone, We added the CRYPTOPP_LIKELY and CRYPTOPP_UNLIKEY macros to help with code generation and branch prediction. Drepper's got a good paper at http://www.akkadia.org/drepper/cpumemory.pdf. It explains the problem and some of the things we can do to help it.
If you think code qualifies for the micro-optimization, then please profile it first. Unix/Linux users can 'make coverage' to get the code coverage statistics. Our first was [mostly] false positive Coverity finding at https://github.com/weidai11/cryptopp/blob/master/gf2n.cpp#L725 . We profiled it and found that offending line executed 555,570 times with no violations. I don't have anything for Windows at the moment. Maybe a Windows user would like to look up the feature and then dial it into misc.h. 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.
