HORIZON HASKELLDocslts/ghc-10.0.xfc4e5982026-10-11Search names, modules, packages, or :: a typeCtrl K

GHC 10.0.0.20260917 · lts/ghc-10.0.x · fc4e598 · 2026-10-11

Modulevulkan-3.27GHC2021

Vulkan.Extensions.VK_AMD_shader_info

Name

VK_AMD_shader_info - device extension

VK_AMD_shader_info

Name String

VK_AMD_shader_info

Extension Type

Device extension

Registered Extension Number

43

Revision

1

Ratification Status

Not ratified

Extension and Version Dependencies

None

Special Use
Contact

Other Extension Metadata

Last Modified Date

2017-10-09

IP Status

No known IP claims.

Contributors

  • Jaakko Konttinen, AMD

Description

This extension adds a way to query certain information about a compiled shader which is part of a pipeline. This information may include shader disassembly, shader binary and various statistics about a shader’s resource usage.

While this extension provides a mechanism for extracting this information, the details regarding the contents or format of this information are not specified by this extension and may be provided by the vendor externally.

Furthermore, all information types are optionally supported, and users should not assume every implementation supports querying every type of information.

New Commands

New Structures

New Enums

New Enum Constants

Examples

This example extracts the register usage of a fragment shader within a particular graphics pipeline:

extern VkDevice device;
extern VkPipeline gfxPipeline;

PFN_vkGetShaderInfoAMD pfnGetShaderInfoAMD = (PFN_vkGetShaderInfoAMD)vkGetDeviceProcAddr(
    device, "vkGetShaderInfoAMD");

VkShaderStatisticsInfoAMD statistics = {};

size_t dataSize = sizeof(statistics);

if (pfnGetShaderInfoAMD(device,
    gfxPipeline,
    VK_SHADER_STAGE_FRAGMENT_BIT,
    VK_SHADER_INFO_TYPE_STATISTICS_AMD,
    &dataSize,
    &statistics) == VK_SUCCESS)
{
    printf("VGPR usage: %d\n", statistics.resourceUsage.numUsedVgprs);
    printf("SGPR usage: %d\n", statistics.resourceUsage.numUsedSgprs);
}

The following example continues the previous example by subsequently attempting to query and print shader disassembly about the fragment shader:

// Query disassembly size (if available)
if (pfnGetShaderInfoAMD(device,
    gfxPipeline,
    VK_SHADER_STAGE_FRAGMENT_BIT,
    VK_SHADER_INFO_TYPE_DISASSEMBLY_AMD,
    &dataSize,
    nullptr) == VK_SUCCESS)
{
    printf("Fragment shader disassembly:\n");

    void* disassembly = malloc(dataSize);

    // Query disassembly and print
    if (pfnGetShaderInfoAMD(device,
        gfxPipeline,
        VK_SHADER_STAGE_FRAGMENT_BIT,
        VK_SHADER_INFO_TYPE_DISASSEMBLY_AMD,
        &dataSize,
        disassembly) == VK_SUCCESS)
    {
        printf((char*)disassembly);
    }

    free(disassembly);
}

Version History

  • Revision 1, 2017-10-09 (Jaakko Konttinen)

    • Initial revision

See Also

No cross-references are available

Document Notes

For more information, see the Vulkan Specification.

This page is a generated document. Fixes and changes should be made to the generator scripts, not directly.

  • 5 types
  • 1 value
  • Packagevulkan-3.27
  • Exports11
  • LanguageGHC2021
  • LicenceBSD-3-Clause
  • SourceVK_AMD_shader_info.hs
valuegetShaderInfoAMD
  1. :: MonadIO io
  2. => Device

    device is the device that created pipeline.

  3. -> Pipeline

    pipeline is the target of the query.

  4. -> ShaderStageFlagBits

    shaderStage is a ShaderStageFlagBits specifying the particular shader within the pipeline about which information is being queried.

  5. -> ShaderInfoTypeAMD

    infoType describes what kind of information is being queried.

  6. -> io (Result, "info" ::: ByteString)
#

vkGetShaderInfoAMD - Get information about a shader in a pipeline

Description

If pInfo is NULL, then the maximum size of the information that can be retrieved about the shader, in bytes, is returned in pInfoSize. Otherwise, pInfoSize must point to a variable set by the application to the size of the buffer, in bytes, pointed to by pInfo, and on return the variable is overwritten with the amount of data actually written to pInfo. If pInfoSize is less than the maximum size that can be retrieved by the pipeline cache, then at most pInfoSize bytes will be written to pInfo, and INCOMPLETE will be returned, instead of SUCCESS, to indicate that not all required of the pipeline cache was returned.

Not all information is available for every shader and implementations may not support all kinds of information for any shader. When a certain type of information is unavailable, the function returns ERROR_FEATURE_NOT_PRESENT.

If information is successfully and fully queried, the function will return SUCCESS.

For infoType SHADER_INFO_TYPE_STATISTICS_AMD, a ShaderStatisticsInfoAMD structure will be written to the buffer pointed to by pInfo. This structure will be populated with statistics regarding the physical device resources used by that shader along with other miscellaneous information and is described in further detail below.

For infoType SHADER_INFO_TYPE_DISASSEMBLY_AMD, pInfo is a pointer to a null-terminated UTF-8 string containing human-readable disassembly. The exact formatting and contents of the disassembly string are vendor-specific.

The formatting and contents of all other types of information, including infoType SHADER_INFO_TYPE_BINARY_AMD, are left to the vendor and are not further specified by this extension.

This query does not behave consistently with the behavior described in Opaque Binary Data Results, for historical reasons.

If the amount of data available is larger than the passed pInfoSize, the query returns up to the size of the passed buffer, and signals overflow with a INCOMPLETE success status instead of returning a ERROR_NOT_ENOUGH_SPACE_KHR error status.

Valid Usage (Implicit)

  • device must be a valid Device handle

  • pipeline must be a valid Pipeline handle

  • shaderStage must be a valid ShaderStageFlagBits value

  • infoType must be a valid ShaderInfoTypeAMD value

  • pInfoSize must be a valid pointer to a size_t value

  • If the value referenced by pInfoSize is not 0, and pInfo is not NULL, pInfo must be a valid pointer to an array of pInfoSize bytes

  • pipeline must have been created, allocated, or retrieved from device

Return Codes

Success
Failure

See Also

VK_AMD_shader_info, Device, Pipeline, ShaderInfoTypeAMD, ShaderStageFlagBits

datadata ShaderResourceUsageAMD
#

VkShaderResourceUsageAMD - Resource usage information about a particular shader within a pipeline

See Also

VK_AMD_shader_info, ShaderStatisticsInfoAMD

Constructors

Instances6Eq, Show, Storable, FromCStruct, ToCStruct, Zero
datadata ShaderStatisticsInfoAMD
#

VkShaderStatisticsInfoAMD - Statistical information about a particular shader within a pipeline

Description

Some implementations may merge multiple logical shader stages together in a single shader. In such cases, shaderStageMask will contain a bitmask of all of the stages that are active within that shader. Consequently, if specifying those stages as input to getShaderInfoAMD, the same output information may be returned for all such shader stage queries.

The number of available VGPRs and SGPRs (numAvailableVgprs and numAvailableSgprs respectively) are the shader-addressable subset of physical registers that is given as a limit to the compiler for register assignment. These values may further be limited by implementations due to performance optimizations where register pressure is a bottleneck.

See Also

VK_AMD_shader_info, ShaderResourceUsageAMD, ShaderStageFlags

Constructors

Instances5Show, Storable, FromCStruct, ToCStruct, Zero
newtypenewtype ShaderInfoTypeAMD
#

VkShaderInfoTypeAMD - Enum specifying which type of shader information to query

Description

See Also

VK_AMD_shader_info, getShaderInfoAMD

Constructors

Instances6Eq, Ord, Read, Show, Storable, Zero