Hi Everyone, I had to make three Clang related check-ins over the last couple of days... It seems my test script was _only_ testing GCC on Linux by taking the default compiler. It never occurred to me to test Clang because Uri I have have thorough coverage on the Macs.
Well, what a surprise when I added http://github.com/weidai11/cryptopp/commit/4cf8d660d29f0533df21c1f29cce8e4e77e10a0c . It uncovered at least three compiler bugs we had to work around for Clang on Linux. I've regression tested Clang on my three Macs, so I _don't_ think I knocked anything out of place. The changes also required us to test on Windows, and I don't think I bumped anything loose there, either. I regression tested on both Windows 7 and Cygwin, and initial results are OK. If the OS X and Windows users would make a quick testing pass, then it would be appreciated. OS X and Linux users can run the gamut by running ' ./cryptest.sh '. I'm especially interested in the custom Clang builds that make their way into /usr/local/bin. I'm running the script now, but the results won't be ready for 3 or 4 hours. Happy holidays to everyone. 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.
