-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Different results depending on endianess #395
Comments
Hi. Thanks for reporting, unfortunately I have no way to access a big endian machine anymore. Have you tried with 2.15? |
Well, I have no direct access to a bigendian machine either. I use Docker + qemu to emulate one within the CI. This can be done also for LittleCMS: https://github.com/sommerluk/Little-CMS/blob/1ee56666795bf695c2e1b24c4a034343bfde0b44/.circleci/config.yml Result for current lcms master: |
Finally I have been able to check the testbed on an very old PowerPC that is true big endian. There is no issue there. |
Indeed, the difference is very small. I only noticed it because I had a failing unit test that checked that the results of a function that relies on LittleCMS are within the given range. Should we close this report as non-issue? |
Sure. Closed as I cannot reproduce it anyway. |
Setup
Consider the following code:
Using LCMS 2.12.0 on Ubuntu Linux 22.04 LTS.
Actual result
For red, green and blue = 0, depending if you are on a big endian or a little endian machine, the value of cielabD50 lightness is different:
Expected results
Additional information
For red, green and blue = 0,001, this results in cielabD50 6.991457e-02 7.569790e-06 7.569790e-06 on both, little endian and big endian machines. Also, for all other higher values, the result on little endian and big endian seem to give identical results.
The text was updated successfully, but these errors were encountered: