On 07/12/17 04:38, Oliver Niebuhr wrote: > BTW: It turned out that the VS SSA-Optimizer is at fault here! After > disabling it with '/d2SSAOptimizer-' blake2b.c compiles fine. > > Seems like a Bug with this Tool Set Version. > > I created a BR: > https://github.com/openssl/openssl/issues/4859 > > Should I create a BR at the VS Forum too?
That would be a good idea! Thanks Matt > > Have a nice Day everyone > Oliver > > On 06/12/2017 15:07, Michael Wojcik wrote: >>> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf >>> Of Oliver Niebuhr >>> Sent: Wednesday, December 06, 2017 08:43 >>> >>> Like mentioned below, I updated the VS 2017 Compiler to 14.12 - but it >>> also happens with 14.11. >> I don't know where those version numbers come from (Microsoft's dev >> toolchain versioning remains a mystery to me), but I'm using VS2017, running >> "cl" with no parameters says 19.11.25547, and I just compiled blake2b.c with >> no issues. >> >> Now, this is blake2b.c from the Argon2 reference implementation - I don't >> know if it's been changed at all in the OpenSSL sources. And I'm not >> building OpenSSL in this case (it's a diffferent project that happens to >> include Argon2), so it's entirely possible I'm using different compiler >> options. But there's another data point, anyway. >> > >
-- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
