| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
I don't expect most of builds to pass since MKL cmake options changed. Addressed this now |
Sorry, something went wrong.
|
I will investigate the following new failures (m6000) from this PR. Interesting though, why cuda stuff failed when change has nothing to do with that backend. The following tests FAILED: 48 - test_homography_cuda (Failed) 80 - test_orb_cuda (Failed) 101 - test_gloh_cuda (Failed) 102 - test_sift_cuda (Failed) |
Sorry, something went wrong.
This new cmake option can take the following values - `Intel-MKL` - Intel MKL is used for blas, fft and sparse related routines - `FFTW/LAPACK/BLAS` - OpenBLAS for blas routines; fftw for fft routines; netlib compatible lapack library for lapack routines - `Intel-MKL` is the default value of this option. We intend to add AMD-AOCL as the third option. To preserve the behavior provided by the old flags, USE_CPU_MKL & USE_OPENCL_MKL, if provided(command-line/cmake-gui) will take precedence even if `AF_COMPUTE_LIBRARY` has `FFTW/LAPACK/BLAS`. Add back vcpkg caching mechanism. The work around we tried so far has increased the build time too much on windows github action Putting vcpkg under arrayfire source root or build folder is making vcpkg think it is in manifest mode and any `vcpkg install` commands are not doing expected standalone dependency installations. Cannot use af_deprecate calls of USE_*_MKL flags, it cannot handle different type cmake variables
| Back | FazBrowse Home | New Git URL |
Description
Build option AF_COMPUTE_LIBRARY to select CPU compute dependency
This new cmake option can take the following values
We intend to add AMD-AOCL as the third option.
To preserve the behavior provided by the old flags, USE_CPU_MKL & USE_OPENCL_MKL, if provided(command-line/cmake-gui) will take precedence even if AF_COMPUTE_LIBRARY has FFTW/LAPACK/BLAS.
Changes to Users
None
Checklist