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
Fix int normalisation when reading in floats with the replacement reader #702
Conversation
…k floating point path. Without this the values were only being scaled to a short's max value.
…acement read functionality. These cover the issue fixed by the previous commit.
Hi @bobsayshilol , thanks for pull request. Do I understand correctly that it was most likely a typo? @erikd , @arthurt , @SoapGentoo , any thoughts? Looks correct to me. |
looks correct to me too. @evpobr could you test it locally, reverting the fix but keeping the test commit and seeing that the test fails without the fix? |
Ok. |
|
@bobsayshilol looks good, please add an entry to |
Yes, that looks like it was the case.
89bed47 looks to have deprecated |
Squash commits to one please before I merge it. |
Can that not be done as part of the merge? https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges#squash-and-merge-your-pull-request-commits |
Thanks @bobsayshilol ! |
This was initially spotted by inspection (I don't have hardware that falls back to using this path) but it was confirmed to be a bug after forcing
psf->ieee_replace
to be enabled inpsf_open_file()
and re-running the test suite.Along with a patch to fix the normalisation, I've also extended
floating_point_test.tpl
to add tests that would have caught the incorrect normalisation.