colordifference_stdc: use float as in SSE #58
Merged
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
The SSE implementation of the function uses single-precision float, whereas this one goes for.... double all over the place.
Extremely unscientific comparisons on godbolt (https://gcc.godbolt.org/z/oa3hP5ffs) shows that both Clang and GCC do much better generating x64 code when float is used. Other SIMD systems should act similarly, but I can't remember the target names. (For more human-like code in clang, try
-Ofast. I could add an attribute or some assumes there, but ehhhh... sounds unnecessary.)PS: It might be a good idea to review other internal uses of
doubletoo. The two cases left appear to be generally sums and other statistics, which I guess is better withdouble, andgamma, which has an externaldoubleAPI.