Closed GoogleCodeExporter closed 8 years ago
I'm suspecting an endian detection problem,
although it's unclear why r118 should be more affected that r117
since the endian detection code has not evolved between those 2 versions...
Could you check that hypothesis by manually forcing endian mode ?
Look for LZ4_BIG_ENDIAN define, and manually override its value please.
Regards
Original comment by yann.col...@gmail.com
on 16 Sep 2014 at 4:37
I'll look into it.
Original comment by yann.col...@gmail.com
on 16 Sep 2014 at 4:40
I created a patch which revise this problem.
I attached.
Original comment by iwama...@gmail.com
on 16 Sep 2014 at 4:41
Attachments:
Hi,
Thanks for your comment.
This is caused by bit size.
s390x is 64bit not 32bit.
Original comment by iwama...@gmail.com
on 16 Sep 2014 at 4:43
OK thanks, so it was the 64-bits detection macro.
I'll correct it for next release.
And when that's possible,
I would also like to get rid of detection macro completely,
relying instead on runtime detection which are much more reliable
(but still trigger some linking errors currently ...)
Original comment by yann.col...@gmail.com
on 16 Sep 2014 at 4:45
Indeed.
However, I think that we cannot avoid this problem when we support C library of
many versions and many CPU's.
But I think about a method to do macro briefly.
Thanks!
Original comment by iwama...@gmail.com
on 16 Sep 2014 at 4:52
Latest "dev" branch release supports your proposed improvement :
https://github.com/Cyan4973/lz4/tree/dev
For your testing
Original comment by yann.col...@gmail.com
on 22 Sep 2014 at 4:39
Fixed into r123
Original comment by yann.col...@gmail.com
on 25 Sep 2014 at 8:41
Original issue reported on code.google.com by
iwama...@gmail.com
on 16 Sep 2014 at 4:05