You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 10, 2023. It is now read-only.
https://github.com/intel/clDNN/blob/master/CMakeLists.txt#L104 causes an issue where systems will compile a binary with avx2 and another binary with avx512. Because CMAKE_BINARY_DIR is not used, whichever binary that was compiled last will override the former. When compiling with different instruction sets or optimizations, distros will create build_avx2 or build_avx512 directories and set CMAKE_BINARY_DIR to one of those. This way different build types do not conflict.
The solution here is NOT to reinvent the wheel by setting binary output to places other than CMAKE_BINARY_DIR.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
https://github.com/intel/clDNN/blob/master/CMakeLists.txt#L104 causes an issue where systems will compile a binary with avx2 and another binary with avx512. Because CMAKE_BINARY_DIR is not used, whichever binary that was compiled last will override the former. When compiling with different instruction sets or optimizations, distros will create build_avx2 or build_avx512 directories and set CMAKE_BINARY_DIR to one of those. This way different build types do not conflict.
The solution here is NOT to reinvent the wheel by setting binary output to places other than CMAKE_BINARY_DIR.
The text was updated successfully, but these errors were encountered: