Open VictorLamoine opened 8 years ago
What about removing this class from the build if SSE is not supported? I.e. conditionally exclude corresponding .h/.cpp files in CMake script. SSE3 and SSE4 detection is broken for me as well.
SSE version checking doesn't work on Linux.
Maybe go with a similar strategy as proposed here.
What about removing this class from the build if SSE is not supported? I.e. conditionally exclude corresponding .h/.cpp files in CMake script.
Given that the class becomes useless, totally agree.
I would propose to add a #error brisk without SSE4.1 support not implemented
so compilation fails. That way we don't provide different headers depending on the host system.
But we don't want compilation of the whole library to fail on non-SSE4.1 systems?
No, only when using the method in question, as in #1522 ;).
Just found that it's actually in the .cpp
file. So not installing the header seems to be the correct way, as taketwo proposed.
We can also have an ifndef
at the top of the header file testing if corresponding HAVE_*
macros are defined by CMake and giving #error
if not. What is the preferred approach?
Marking this as stale due to 30 days of inactivity. It will be closed in 7 days if no further activity occurs.
Is this still something to be added on todo list or has this been resolved?
Reported on the mailing-list.
My CPU info (supports SSE 4.1 and SSE 4.2):
Example program output (see mailing-list for the example data)
More debug info is available on the mailing-list.