10-12-2018, 08:15 AM
(This post was last modified: 10-12-2018, 08:19 AM by mbtaylor1982.)
(10-12-2018, 03:24 AM)Alexandre Machado Wrote: About zlib-ng, it was also considered. However, 6 months ago it didn't look production ready (I'm not convinced yet, check out this issue: https://github.com/Dead2/zlib-ng/issues/90). There are reported bugs which caused application crash which are still open. This branch contains massive modifications to the main zlib branch and, at that time, we couldn't find anyone using it in production. It would be basically a gamble. Intel and Cloudflare branches have their own issues, but they have been reported to be stable.
In case someone desperately needs to deploy to an old processor, you can still use x86 binary which doesn't require AVX at all.
We are still investigating this issue, so we should have more information soon.
Cheers
Thanks for looking into it, for now we will simply modify our copy of the source to use Define USE_ZLIB_1211 for our 64 Bit apps. hopefully a more permanent fix can be found.
Initially i was trying to see if there was a way to detect the CPU features and bind the appropriate zlib version at run time rather than compile time.
As for zlib-ng I would stay well clear until a stable version is released. Looking at the Cloud Flare source code (although i'm no expert in this) it looks as if there is some detection of CPU instruction sets going on now, but I'm not sure if its at compile or run time.
It’s not a bug – it’s an undocumented feature.