How to build MIOpen.dll on Windows

[scarsty]

Install VS 2022, ninja, cmake, rocm, and so on.
Install vcpkg, and use it to install bz2, sqlite3, nlohmann_json, boost.
Sometimes CMAKE_PREFIX_PATH on Windows only recognize the first path, so copy all rocm files to vcpkg's lib path (ex: d:/project/microsoft/vcpkg/installed/x64-windows/).
Copy bzcat.exe and bzip2.dll to some bin PATH.
Open ./CMakeFiles.txt, at line 70, remove 0.7.3 REQUIRED.
Create unistd.h yourself.

#ifndef _UNISTD_H

#define _UNISTD_H
#include <io.h>
#include <process.h>
#endif /* _UNISTD_H */

Download half.hpp from https://github.com/ROCm/half/blob/master/web/half.hpp, copy it to include PATH.
Copy boost_filesystem-vc140-mt.lib to libboost_filesystem-vc71-mt.lib (it is confused to how cmake guess the file name).
Something about amd_comgr (head and cmake files) are lost, copy them from somewhere. Linux version may be useful.

Use x64 native tools command prompt of VS 2022 to enter cmd, switch to the path of MIOpen.

mkdir build
cd build

cmake .. -DMIOPEN_BACKEND=HIP -DCMAKE_PREFIX_PATH="D:\project\microsoft\vcpkg\installed\x64-windows" -G "Ninja" -DMIOPEN_USE_MLIR=Off -DMIOPEN_ENABLE_AI_KERNEL_TUNING=Off -DMIOPEN_ENABLE_AI_IMMED_MODE_FALLBACK=Off -DHALF_INCLUDE_DIR="d:/project/microsoft/vcpkg/installed/x64-windows/include" -DMIOPEN_USE_COMPOSABLEKERNEL=Off -DCMAKE_MAKE_PROGRAM=ninja.exe -DCMAKE_C_COMPILER="d:/project/microsoft/vcpkg/installed/x64-windows/bin/clang.exe" -DMIOPEN_SQLITE3_USE_SYSTEM=On -DHIP_PLATFORM="amd" -DBoost_DEBUG=ON -DBoost_INCLUDE_DIR="d:/project/microsoft/vcpkg/installed/x64-windows/include" -DBUILD_TESTING=Off

ninja

Some options have been closed, I do not make sure they are the reason to slow speed or not. The dependencies are harder to build.

Then you can get miopen.dll, but it seems has some bugs. Maybe we have to wait for rocm 6 for windows.

miopenFindConvolutionForwardAlgorithm will get:

MIOpen(HIP): Error [Compile] 'hiprtcCompileProgram(prog.get(), c_options.size(), c_options.data())' naive_conv.cpp: HIPRTC_ERROR_COMPILATION (6)
MIOpen(HIP): Error [BuildHip] HIPRTC status = HIPRTC_ERROR_COMPILATION (6), source file: naive_conv.cpp
MIOpen(HIP): Warning [BuildHip] error: unknown argument: '-fno-offload-uniform-block'
In file included from C:\Users\sty\AppData\Local\Temp\comgr-8d61c2\input\naive_conv.cpp:32:
In file included from C:\Users\sty\AppData\Local\Temp\comgr-8d61c2\include\miopen_limits.hpp:96:
In file included from C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.37.32822\include\limits:15:
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.37.32822\include\xtr1common:21:8: error: redefinition of 'integral_constant'
struct integral_constant {

[scarsty]

@johnnynunez @Sabrewarrior
Maybe you can try it. Let me know if you met some bump.

[johnnynunez]

thanks! I have experience in linux but not much in windows.
Can you share the binaries?

[scarsty]

thanks! I have experience in linux but not much in windows. Can you share the binaries?

https://drive.google.com/file/d/1GV4MaYiKaUdZmGY3Hgn8r-eBwAJdxDNB/view?usp=sharing
as I mentioned, it still has some bugs.

[lshqqytiger]

I have a question.

-DCMAKE_C_COMPILER="d:/project/microsoft/vcpkg/installed/x64-windows/bin/clang.exe"

Is this "clang.exe" from ROCm/bin or not?
I'm getting this error with clang.exe from ROCm on running ninja after cmake.

clang++: error: cannot find ROCm device library; provide its path via '--rocm-path' or '--rocm-device-lib-path', or pass '-nogpulib' to build without ROCm device library

[lshqqytiger]

I had to replace DEFINES = with DEFINES = --rocm-path="path/to/rocm/5.7" in build.ninja file.
Also, I think it is not https://github.com/ROCm/half/blob/master/web/half.hpp, but https://github.com/ROCm/half/blob/master/include/half.hpp.
Nevertheless, I'm failing at the almost final step.

[484/486] Linking CXX shared library bin\MIOpen.dll
FAILED: bin/MIOpen.dll lib/MIOpen.lib
C:\Windows\system32\cmd.exe /C "cd . && path\to\MIOpen\vcpkg_installed\x64-windows\bin\clang++.exe -fuse-ld=lld-link -nostartfiles -nostdlib -O3 -DNDEBUG -D_DLL -D_MT -Xclang --dependent-lib=msvcrt  -pthread -shared -o bin\MIOpen.dll  -Xlinker /MANIFEST:EMBED -Xlinker /implib:lib\MIOpen.lib -Xlinker /pdb:bin\MIOpen.pdb -Xlinker /version:0.0 @CMakeFiles\MIOpen.rsp  && cd ."
clang++: warning: argument unused during compilation: '-pthread' [-Wunused-command-line-argument]
lld-link: error: path/to/ROCm/5.7/bin/amd_comgr0507.dll: bad file type. Did you specify a DLL instead of an import library?
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
[485/486] Building CXX object driver/CMakeFiles/MIOpenDriver.dir/main.cpp.obj
ninja: build stopped: subcommand failed.

[lshqqytiger]

I replaced bin/amd_comgr0507.dll with lib/amd_comgr0507.lib in build.ninja file, and now I can build MIOpen. Thanks.

[scarsty]

In fact some tricks are still needed. And some errors occur when trying to compute a convolution with the dll.

[A-Ghorab]

Any updates with the new version?

[lshqqytiger]

https://drive.google.com/file/d/1EJuzk3y9LjXKb1qeMqK5r7IgbjDQzIYR/view?usp=sharing outdated
MIOpen built with rocMLIR. (without composable kernel)
ROCm 5.7 Windows
0334279

[scarsty]

https://drive.google.com/file/d/1EJuzk3y9LjXKb1qeMqK5r7IgbjDQzIYR/view?usp=sharing MIOpen built with rocMLIR. (without composable kernel) ROCm 5.7 Windows 0334279

I got MIOpen Error: E:/ML/MIOpen/src/ocl/convolutionocl.cpp:536: No invoker was registered for convolution forward. Was find executed?, do you have any suggestions?

[scarsty]

Mmmm....
Sometimes I cannot understand what is amd thinking about.
It had worked with rocm 5.5 but now it can not.

[lshqqytiger]

You can try my custom build with some PR merged.
https://drive.google.com/file/d/1y-Es_aBZfBmTdY_ZM_90xFxB8BfFV6Q6/view?usp=sharing
(It is large as it includes *.kdb files)
It works for me.

[scarsty]

This build works fine for me.
And did you test the performance of it? I have tried to train MNIST with a simple lenet, 7900 xtx is about 20% slower than rtx 2080, I think this is far away from that it should have.

[lshqqytiger]

I didn't. Even if I can't build with composable kernel, it sounds quite slow for me too.

[scarsty]

So I am still expecting for an official version...