oyvindln
oyvindln
Which version of miniz_oxide is it using? There was a bug introduced in miniz_oxide 0.8.3 that I fixed in 0.8.5 that caused corrupt output in this case so maybe rust...
If you run ```cargo update``` it should update to the latest version.
Yeah as far as I know rust still lacks a way to directly heap allocate a struct that is guaranteed to avoid the stack even in debug mode without resorting...
We already do that with simd_adler32. I think it's acceptable to do it behind optional features if it provides some significant benefit (or has some other demonstrable use case in...
I'm not done fixing it yet as it's still an order of magnitude slower than it should be, but I've started doing some work on it to split the stored...
I'm not able to reproduce on my travel laptop though I'm using OpenSUSE on it. Can't test on Ubuntu until I'm back home in a bit more than a week....
also just realized - if using a vm anyway maybe it's faster/better to just do a native build from a x86 t2 install?
Thanks for the ping - this does look like it could be a regression in miniz_oxide. I can do some testing on my android TV box that runs armv7 android...
Hm, would have to investigate that as well then
Seeing as this seems to be how the original miniz behaves and is designed around I think it makes sense to keep this as the default behaviour (though document it...