Conversation
|
What's the point here exactly ? DYNAMIC_ARCH is useless with MSVC as that compiler does not support the assembly kernels. Though the compile error you saw comes earlier and is probably a result of MSVC not supporting the indirections that define GEMM_UNROLL_MN for a particular target, and/or computation of a constant from preprocessor variables. |
|
Sorry if this came across as a bug report. It was meant to be a "proper" PR. I started with build rules that were pretty similar to the ones used for MinGW (with MSYS2). My comments were meant to describe why there are differences. Sorry for not making that clearer before. Thank you for answering the questions I had. If I misunderstood what you meant in #4263, feel free to close this PR. |
This adds GitHub hosted runners using the MSVC compiler on Windows.
I tried to build with
-DDYNAMIC_ARCH=ON. But that failed with:I don't know if that means that there is an issue with DYNAMIC_ARCH in general for that compiler or if that is caused by something else.
I also don't know if
-DTARGET=CORE2is a good choice in that case. Please, let me know if that should be changed.Since I ended up not building with DYNAMIC_ARCH, I didn't add these rules to
dynamic_arch.yaml.CMake warned during configure that building shared and static libraries at the same time is unsupported. So, I opted for building both separately in a matrix. (Do you know why that is unsupported?)
I didn't try yet to figure out how to bring a Fortran compiler into this mix. It's building with
-DC_LAPACK=ONinstead.I see a different test is run on Azure for
Windows_cl(openblas_utest.exe). Should that be run here, too?