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
>
>
Morning.
Yeah my fault. I mixed up CL and Link Version Numbers:
Link Version is 14.12.25830.2 and
CL Version 19.12.25830.2 but
Compiler Tool Set Version is 14.12
You have to love their Versioning Scheme ;)
BTW: It turned out that the VS SSA-Optimizer is at fault here! After
disabling it with '/d
> 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 (Micros
Hi.
Like mentioned below, I updated the VS 2017 Compiler to 14.12 - but it
also happens with 14.11.
Problem is: There is No Error Message of any kind - CL.exe keeps running
(well more or less) indefinitely. It simply stops working.
It really seems like a Compiler Bug. But I am too OpenSSL noobis
On 06/12/17 08:24, Oliver Niebuhr wrote:
> Hello.
>
> I am not sure if it is a VS Compiler Bug or a Bug in OpenSSL.
>
> When the Compiler reaches 'Blake2b.c', it creates the 'Blake2b.obj' and
> then hangs indefinitely.
>
> CPU usage for CL stays at 27-28 Percent. Used RAM stays at 34-35 Megaby
Hello.
I am not sure if it is a VS Compiler Bug or a Bug in OpenSSL.
When the Compiler reaches 'Blake2b.c', it creates the 'Blake2b.obj' and
then hangs indefinitely.
CPU usage for CL stays at 27-28 Percent. Used RAM stays at 34-35 Megabyte.
OpenSSL Version: 1.1.0 Git up2date, Static and Dynamic
