Build and Install Instructions¶
AMD’s library for high performance machine learning primitives. Sources and binaries can be found at MIOpen’s GitHub site.
MIOpen supports two programming models -
- A ROCm enabled platform, more info here
- Base software stack, which includes
- OpenCL - OpenCL libraries and header files
- HIP -
- HIP and HCC libraries and header files
- clang-ocl – required
- MIOpenGEMM to enable various functionalities including transposed and dilated convolutions
- ROCm cmake modules can be installed from here
- Half - IEEE 754-based half-precision floating point library
- Boost at least version 1.58
- MIOpen uses
boost-filesystempackages to enable persistent kernel cache
- MIOpen uses
- rocBlas Minimum version branch master-rocm-2.6
Installing MIOpen with pre-built packages¶
MIOpen can be installed on Ubuntu using
For OpenCL backend:
apt-get install miopen-opencl
For HIP backend:
apt-get install miopen-hip
Currently both the backends cannot be installed on the same system simultaneously. If a different backend other than what currently exists on the system is desired, please uninstall the existing backend completely and then install the new backend.
Installing the dependencies¶
The dependencies can be installed with the
cmake -P install_deps.cmake
This will install by default to
/usr/local but it can be installed in another location with
cmake -P install_deps.cmake --prefix /some/local/dir
This prefix can used to specify the dependency path during the configuration phase using the
MIOpen’s HIP backend uses rocBlas by default. Users can install rocBlas minimum release by using
apt-get install rocblas. To disable using rocBlas set the configuration flag
-DMIOPEN_USE_ROCBLAS=Off. rocBlas is not available for the OpenCL backend.
Installing minimum dependencies in ROCm environment¶
Users who are working in a fully installed and up to date ROCm environment may not wish to additionally install rocm-cmake, clang-ocl, MIOpenGEMM, or rocBLAS. This can be done by simply inserting the command
--minimum into the cmake command as shown below:
cmake -P install_deps.cmake --minimum --prefix /some/local/dir
This will build the Boost and half libraries.
Building MIOpen from source¶
Configuring with cmake¶
First create a build directory:
mkdir build; cd build;
Next configure cmake. The preferred backend for MIOpen can be set using the
-DMIOPEN_BACKEND cmake variable.
For OpenCL, run:¶
cmake -DMIOPEN_BACKEND=OpenCL ..
The above assumes that OpenCL is installed in one of the standard locations. If not, then manually set these two cmake variables:
cmake -DMIOPEN_BACKEND=OpenCL -DOPENCL_LIBRARIES=<opencl-library-path> -DOPENCL_INCLUDE_DIRS=<opencl-headers-path> ..
And an example setting the dependency path:
cmake -DMIOPEN_BACKEND=OpenCL -DCMAKE_PREFIX_PATH=/some/local/dir ..
For HIP, run:¶
Set the C++ compiler to
export CXX=<location-of-hcc-compiler> cmake -DMIOPEN_BACKEND=HIP -DCMAKE_PREFIX_PATH="<hip-installed-path>;<hcc-installed-path>;<clang-ocl-installed-path>" ..
An example cmake step can be:
CXX=/opt/rocm/hcc/bin/hcc cmake -DMIOPEN_BACKEND=HIP -DCMAKE_PREFIX_PATH="/opt/rocm/hcc;/opt/rocm/hip" ..
Setting Up Locations¶
By default the install location is set to ‘/opt/rocm’, this can be set by using
cmake -DMIOPEN_BACKEND=OpenCL -DCMAKE_INSTALL_PREFIX=<miopen-installed-path> ..
System Performance Database and User Database¶
The default path to the System PerfDb is
miopen/share/miopen/db/ within install location. The default path to the User PerfDb is
~/.config/miopen/. For development purposes, setting
BUILD_DEV will change default path to both database files to the source directory:
cmake -DMIOPEN_BACKEND=OpenCL -DBUILD_DEV=On ..
Database paths can be explicitly customized by means of
MIOPEN_SYSTEM_DB_PATH (System PerfDb) and
MIOPEN_USER_DB_PATH (User PerfDb) cmake variables.
If the user installs a new version of MIOpen, it is recommended that the user move, or delete their old user database file. The user can find the file with the suffix
*.updb.txt in the user perf db path.
More information about the performance database can be found here.
Persistent Program Cache¶
MIOpen by default caches the device programs in the location
~/.cache/miopen/. In the cache directory there exists a directory for each version of MIOpen. Users change the location of the cache directory during configuration using the flag
Users can also disable the cache during runtime using the environmental variable set as
If the compiler changes, or the user modifies the kernels then the cache must be deleted for the MIOpen version in use; e.g.,
rm -rf ~/.cache/miopen/<miopen-version-number>. More information about the cache can be found here.
Changing the cmake configuration¶
The configuration can be changed after running cmake by using
ccmake .. OR
ccmake program is not available on windows.
Building the library¶
The library can be built, from the
build directory using the ‘Release’ configuration:
cmake --build . --config Release OR
And can be installed by using the ‘install’ target:
cmake --build . --config Release --target install OR
This will install the library to the
CMAKE_INSTALL_PREFIX path that was set.
Building the driver¶
MIOpen provides an application-driver which can be used to execute any one particular layer in isolation and measure performance and verification of the library.
The driver can be built using the
cmake --build . --config Release --target MIOpenDriver OR
Documentation on how to run the driver is here.
Running the tests¶
The tests can be run by using the ‘check’ target:
cmake --build . --config Release --target check OR
A single test can be built and ran, by doing:
cmake --build . --config Release --target test_tensor ./bin/test_tensor
Building the documentation¶
HTML and PDF documentation can be built using:
cmake --build . --config Release --target doc OR
This will build a local searchable web site inside the ./MIOpen/doc/html folder and a PDF document inside the ./MIOpen/doc/pdf folder.
Documentation is built using generated using Doxygen and should be installed separately.
Requirements for both Sphinx, Breathe, and the ReadTheDocs theme can be filled for these in the MIOpen/doc folder:
pip install -r ./requirements.txt
Depending on your setup
sudo may be required for the pip install.
Formatting the code¶
All the code is formatted using clang-format. To format a file, use:
clang-format-3.8 -style=file -i <path-to-source-file>
Also, githooks can be installed to format the code per-commit:
Installing the dependencies manually¶
If Ubuntu v16 is used then the
Boost packages can also be installed by:
sudo apt-get install libboost-dev sudo apt-get install libboost-system-dev sudo apt-get install libboost-filesystem-dev
Note: MIOpen by default will attempt to build with Boost statically linked libraries. If it is needed, the user can build with dynamically linked Boost libraries by using this flag during the configruation stage:
however, this is not recommended.
half header needs to be installed from here.
The easiest way is to use docker. You can build the top-level docker file:
docker build -t miopen .
Then to enter the development environment use
docker run --device='/dev/kfd' --device='/dev/dri' -v=`pwd`:/data -w /data --group-add video -it miopen