Adam Stylinski

Also, if the user does manage to do this, and the allocator is not an aligning allocator, won't this break code that assumes aligned allocations? There are a few places...

Ahhh, I guess the fact that it's a mismatched free then this doesn't become an issue. And I guess given that an allocator will always only over allocate and not...

Perhaps we can provide a permanent URL in the warning message that provides a lineage to the zlib manual to explain what the user is doing wrong? We've run into...

> > Perhaps we can provide a permanent URL in the warning message that provides a lineage to the zlib manual to explain what the user is doing wrong? We've...

I agree and our number of allocations in inflate and deflate are limited but I do worry it'd draw the ire of a lot of users incidentally using zlib-ng, such...

This is a bug in the proprietary library, even with zlib. Check out this entry in the zlib manual https://www.zlib.net/manual.html#Usage The fact that it doesn't cause an issue with zlib...

Do you know what z_alloc and z_free are defined as in this code? If it happens to be the zlib wrappers for alloc and free and it's a superfluous assignment,...

@jo-oe thanks for notifying mono so they can fix it on their end. I'm not sure what to do about the downstream consumers that are very unlikely to repackage fixed...

I have a g5, I can try it out tomorrow.

Code doesn't currently compile - it doesn't seem to like the ALIGNED macro: ``` In file included from /home/adam/zlib-ng-unaligned/tools/makefixed.c:5: /home/adam/zlib-ng-unaligned/inflate.h:106:34: error: expected declaration specifiers or ‘...’ before numeric constant 106...