Closed pedromfcarvalho closed 4 years ago
Expected. A future processor may change this behavior.
@abalib Do you have any references to this behavior?
@tuliom Unfortunately no. We should make a remark in a README. Something like this
Internal state of nx-gzip hardware is randomly initialized which may result in compressed stream sizes slightly different between multiple runs of the same input. Use deflateBound() instead to estimate output buffer sizes instead of calling deflate() twice.
I will reopen when it's time for the next processor
The sample code gzip_nxfht_test in the samples/ directory produces a compressed result that varies in size from one invocation to the other, when applied to alice29.txt, also in samples:
The more common case is 75543 bytes, but it sometimes changes. I don't know if is supposed to be non-deterministic, sometimes the sample will always produce 75543 bytes, but sometimes it produces other sizes.