Browse by type
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: * RDNA™ and GCN ISA disassembly * Intermediate language disassembly: AMDIL, DXIL and DXBC for DirectX, SPIR-V for Vulkan, LLVM IR for Offline OpenCL * Hardware resource usage statistics, such as register consumption, static memory allocation and more * Compiled binaries * Live register analysis (see http://gpuopen.com/learn/live-vgpr-analysis-radeon-gpu-analyzer/ for more info) * Control flow graphs * Build errors and warnings
The RGA package contains both a GUI app and a command-line executable.
The supported modes by the GUI app are: * Vulkan - GLSL/SPIR-V as input, together with the Vulkan pipeline state; compiled through AMD's Vulkan driver * OpenCL - AMD's LLVM-based Lightning Compiler for OpenCL * Binary Analysis - analyze pre-compiled AMD GPU Code Object binary files
The supported modes by the command-line tool are: * Binary Analysis - analyze pre-compiled AMD GPU Code Object binary files * DX12 (see https://gpuopen.com/radeon-gpu-analyzer-2-2-direct3d12-compute/ and https://gpuopen.com/radeon-gpu-analyzer-2-3-direct3d-12-graphics/ for more details) * DX11 * DXR * Vulkan - compilation of GLSL/SPIR-V together with the API's pipeline state, using AMD's Vulkan driver * Vulkan Offline - using a static compiler, accepts GLSL/SPIR-V as input. Note: to ensure that the results that RGA provides are accurate and reflect the real-world case, please use the new Vulkan live driver mode (which is also supported in the GUI application). * OpenCL - AMD's LLVM-based Lightning Compiler for Offline OpenCL * OpenGL
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: * Vulkan offline mode * OpenCL mode * OpenGL mode * DX11 mode * Binary Analysis mode
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: * CMake 3.10 or above is required for Visual Studio 2019. CMake 3.21 or above is required for Visual Studio 2022. For auto-detecting the Vulkan SDK version 3.7 or above is required. * Python 3.10 or above * Qt (in case that you are interested in building the GUI app; you can build the command line executable without Qt). Qt 6.7.0 is recommended.
cd to the build sub-folder, and run:
python pre_build.py --qt <version of QT> --vs 2019
Where is the version of QT to be used with the script, such as 6.7.0 (default is 6.7.0).
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: * RadeonGPUAnalyzerCLI project for the command line executable * RadeonGPUAnalyzerGUI project for the GUI app
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 exit
If 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).
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:i386To build the GUI app, you should also have Qt installed
Build:
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 6.7.0 --vk-include ~/work/vulkan-sdk/1.2.162.1/x86_64/include/ --vk-lib ~/work/vulkan-sdk/1.2.162.1/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.pyrun: cmake –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 directory
* mkdir _build
* cd _build
* cmake –DCMAKE_BUILD_TYPE=Release ../
* run: make
Run 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: * RDNA™ and GCN ISA disassembly * Intermediate language disassembly: AMDIL, DXIL and DXBC for DirectX, SPIR-V for Vulkan, LLVM IR for Offline OpenCL * Hardware resource usage statistics, such as register consumption, static memory allocation and more * Compiled binaries * Live register analysis (see http://gpuopen.com/learn/live-vgpr-analysis-radeon-gpu-analyzer/ for more info) * Control flow graphs * Build errors and warnings
The RGA package contains both a GUI app and a command-line executable.
The supported modes by the GUI app are: * Vulkan - GLSL/SPIR-V as input, together with the Vulkan pipeline state; compiled through AMD's Vulkan driver * OpenCL - AMD's LLVM-based Lightning Compiler for OpenCL * Binary Analysis - Analyze pre-compiled binary Code Object files
The supported modes by the command-line tool are: * Binary Analysis - Analyze pre-compiled binary Code Object files. * DX12 (see https://gpuopen.com/radeon-gpu-analyzer-2-2-direct3d12-compute/ and https://gpuopen.com/radeon-gpu-analyzer-2-3-direct3d-12-graphics/ for more details) * DX11 * DXR * Vulkan - compilation of GLSL/SPIR-V together with the API's pipeline state, using AMD's Vulkan driver * Vulkan Offline - using a static compiler, accepts GLSL/SPIR-V as input. Note: to ensure that the results that RGA provides are accurate and reflect the real-world case, please use the new Vulkan live driver mode (which is also supported in the GUI application). * OpenCL - AMD's LLVM-based Lightning Compiler for Offline OpenCL * OpenGL * AMDIL
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: * Vulkan offline mode * OpenCL offline mode * Dx11 * OpenGL * Binary Anslysis mode
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: * CMake 3.10 or above. For auto-detecting the Vulkan SDK version 3.7 or above is required. * Python 3.10 or above * Qt (in case that you are interested in building the GUI app; you can build the command line executable without Qt). Qt 6.7.0 is recommended.
cd to the build sub-folder, and run:
python pre_build.py --qt <version of Qt> --vs 2019
Where is the version of QT to be used with the script, such as 6.7.0 (default is 6.7.0).
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: * RadeonGPUAnalyzerCLI project for the command line executable * RadeonGPUAnalyzerGUI project for the GUI app
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 exit
If 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).
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:i386sudo apt-get install patchelfTo build the GUI app, you should also have Qt installed
Build:
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 6.7.0 --vk-include ~/work/vulkan-sdk/1.2.162.1/x86_64/include/ --
$ claude mcp add radeon_gpu_analyzer \
-- python -m otcore.mcp_server <graph>