Radeon GPU Analyzer is a compiler and code analysis tool for Vulkan®, DirectX®, OpenGL® and OpenCL™. Using this product, you can compile high-level source code for a variety of AMD GPU and APU architectures, independent of the type of GPU/APU that is physically installed on your system.
You can use RGA to produce the following output:
The RGA package contains both a GUI app and a command-line executable.
The supported modes by the GUI app are:
The supported modes by the command-line tool are:
To run the tool, you would need to have the AMD Radeon Adrenalin Software (Windows) or amdgpu-pro driver (Linux) installed for all modes, except for the following "offline" modes, which are independent of the driver and hardware:
For the non-offline modes, it is strongly recommended to run with the latest drivers so that the latest compiler is used and the latest architectures can be targeted.
A specific note for Vulkan mode users:
RGA releases are packaged with the AMD Vulkan driver to enable users who run on machines without an AMD GPU or driver. This is not the case if you build the tool yourself. To enable a custom RGA build on a non-AMD machine, copy the "amdvlk" folder from an RGA release archive to your build output folder (make sure to place the folder in the same folder hierarchy as in the release archive). Please note that this is a workaround and not the recommended configuration.
As a preliminary step, make sure that you have the following installed on your system:
cd to the build sub-folder, and run:
python pre_build.py --qt <version of QT> --vs 2019Where
Running the pre_build.py script will fetch all the dependencies and generate the solution file for Visual Studio. After successfully running the pre_build.py script, open RGA.sln from build\windows\vs2019 (or vs2017), and build:
Some useful options of the pre_build.py script:
--vs <VS version>: generate the solution files for a specific Visual Studio version. For example, to target VS 2022, add --vs 2022 to the command.--qt <Qt version>: specify the version of QT to be used with the script. By default, CMake would try to auto-detect Qt on the system.--vk-include and --vk-lib: full paths to where the Vulkan SDK include and Vulkan lib folders. By default, CMake would try to auto-detect the Vulkan SDK on the system.--help: show help message and exitIf you are intending to analyze DirectX 11 shaders using RGA, copy the x64 version of Microsoft's D3D compiler to a subdirectory named "utils" under the RGA executable's directory (for example, D3DCompiler_47.dll).
-=-
If for some reason you do not want to use the pre_build.py script, you can also manually fetch the dependencies and generate the solution and project files: Start by running the fetch_dependencies.py script to fetch the solution's dependencies. To generate the solution file for VS 2019 in x64 configuration, use:
cmake.exe -G "Visual Studio 16 2019 Win64" <full path to the RGA repo directory>If you are intending to analyze DirectX shaders using RGA, copy the x64 version of Microsoft's D3D compiler to a subdirectory named "utils" under the RGA executable's directory (for example, D3DCompiler_47.dll).
One time setup:
sudo apt-get install libboost-all-devsudo apt-get install gcc-multilib g++-multilibsudo apt-get install libglu1-mesa-dev mesa-common-dev libgtk2.0-devsudo apt-get install zlib1g-dev libx11-dev:i386Build:
cd to the Build sub-folder
On Linux, it is recommended to explicitly pass to CMake the location of the Vulkan SDK include and lib directories as well as the location of Qt. For example:
python pre_build.py --qt 5.15.2 --vk-include ~/work/vulkan-sdk/1.1.97.0/x86_64/include/ --vk-lib ~/work/vulkan-sdk/1.1.97.0/x86_64/lib/This will fetch all the dependencies and generate the make files.
Then, cd to the auto-generated subfolder build/linux/make and run make.
-=-
If for some reason you do not want to use the pre_build.py script, you can also manually fetch the dependencies and generate the makefiles:
python fetch_dependencies.pycmake –DCMAKE_BUILD_TYPE=Release (or: Debug) <full or relative path to the RGA repo directory>It is recommended to create a directory to hold all build files, and launch cmake from that directory.
For example:
mkdir _buildcd _buildcmake –DCMAKE_BUILD_TYPE=Release ../makeRun the RadeonGPUAnalyzerGUI executable. The app provides a quickstart guide and a help manual under Help.
Radeon GPU Analyzer is a compiler and code analysis tool for Vulkan®, DirectX®, OpenGL® and OpenCL™. Using this product, you can compile high-level source code for a variety of AMD GPU and APU architectures, independent of the type of GPU/APU that is physically installed on your system.
You can use RGA to produce the following output:
The RGA package contains both a GUI app and a command-line executable.
The supported modes by the GUI app are:
The supported modes by the command-line tool are:
To run the tool, you would need to have the AMD Radeon Adrenalin Software (Windows) or amdgpu-pro driver (Linux) installed for all modes, except for the following "offline" modes, which are independent of the driver and hardware:
For the non-offline modes, it is strongly recommended to run with the latest drivers so that the latest compiler is used and the latest architectures can be targeted.
A specific note for Vulkan mode users:
RGA releases are packaged with the AMD Vulkan driver to enable users who run on machines without an AMD GPU or driver. This is not the case if you build the tool yourself. To enable a custom RGA build on a non-AMD machine, copy the "amdvlk" folder from an RGA release archive to your build output folder (make sure to place the folder in the same folder hierarchy as in the release archive). Please note that this is a workaround and not the recommended configuration.
As a preliminary step, make sure that you have the following installed on your system:
cd to the build sub-folder, and run:
python pre_build.py --qt <version of Qt> --vs 2019Where
Running the pre_build script will fetch all the dependencies and generate the solution file for Visual Studio. After successfully running the preuild script, open RGA.sln from build\windows\vs2019 (or vs2017), and build:
Some useful options of the pre_build.py script:
--vs <VS version>: generate the solution files for a specific Visual Studio version. For example, to target VS 2019, add --vs 2019 to the command.--qt <Qt version>: specify the version of QT to be used with the script. By default, CMake would try to auto-detect Qt on the system.--vk-include and --vk-lib: full paths to where the Vulkan SDK include and Vulkan lib folders. By default, CMake would try to auto-detect the Vulkan SDK on the system.--help: show help message and exitIf you are intending to analyze DirectX 11 shaders using RGA, copy the x64 version of Microsoft's D3D compiler to a subdirectory named "utils" under the RGA executable's directory (for example, D3DCompiler_47.dll).
-=-
If for some reason you do not want to use the pre_build.py script, you can also manually fetch the dependencies and generate the solution and project files: Start by running the FetchDependencies.py script to fetch the solution's dependencies. To generate the solution file for VS 2017 in x64 configuration, use:
cmake.exe -G "Visual Studio 16 2019 Win64" <full path to the RGA repo directory>If you are intending to analyze DirectX shaders using RGA, copy the x64 version of Microsoft's D3D compiler to a subdirectory named "utils" under the RGA executable's directory (for example, D3DCompiler_47.dll).
One time setup:
sudo apt-get install libboost-all-devsudo apt-get install gcc-multilib g++-multilibsudo apt-get install libglu1-mesa-dev mesa-common-dev libgtk2.0-devsudo apt-get install zlib1g-dev libx11-dev:i386Build:
cd to the Build sub-folder
On Linux, it is recommended to explicitly pass to CMake the location of the Vulkan SDK include and lib directories as well as the location of Qt. For example:
python pre_build.py --qt 5.15.2 --vk-include ~/work/vulkan-sdk/1.1.97.0/x86_64/include/ --vk-lib ~/work/vulkan-sdk/1.1.97.0/x86_64/lib/This will fetch all the dependencies and generate the make files.
Then, cdto the auto-generated subfolder build/linux/make and run make.
-=-
If for some reason you do not want to use the pre_build.py script, you can also manually fetch the dependencies and generate the makefiles:
python fetch_dependencies.pycmake –DCMAKE_BUILD_TYPE=Release (or: Debug) <full or relative path to the RGA repo directory>It is recommended to create a directory to hold all build files, and launch cmake from that directory.
For example:
cd to the RGA repo directorymkdir _buildcd _buildcmake –DCMAKE_BUILD_TYPE=Release ../makeRun the RadeonGPUAnalyzerGUI executable. The app provides a quickstart guide and a help manual under Help.
Run the rga executable.
Usage:
rga -h rga -s bin -hrga -s dx12 -hrga -s dx11 -hrga -s dxr -hNote: RGA's DX11 mode requires Microsoft's D3D Compiler DLL in runtime. If you copy the relevant D3D Compiler DLL to the utils subdirectory under the executable's directory, RGA will use that DLL in runtime. The default D3D compiler that RGA public releases ship with is d3dcompiler_47.dll.
rga -s opengl -hrga -s opencl -hrga -s vulkan -hrga -s vk-offline -hrga -s vk-offline-spv -hrga -s vk-offline-spv-txt -hFor support, please visit the RGA repository github page: https://github.com/GPUOpen-Tools/RGA
The source code of this product is being reformatted to follow the Google C++ Style Guide https://google.github.io/styleguide/cppguide.html
In the interim you may encounter a mix of both an older C++ coding style, as well as the newer Google C++ Style.
Please refer to the _clang-format file in the root directory of the product for additional style information.
Radeon GPU Analyzer is licensed under the MIT license. See the License.txt file for complete license information.
Please see RGA_NOTICES.txt for copyright and third party license information.