Skip to content

[SPIRV] SPIRV Backend lacks a clear way to determine execution model #167562

@Alexander-Johnston

Description

@Alexander-Johnston

Currently the SPIRVSubtarget class has limited ability to determine the current execution model. It provides distinction between Kernel and Shader environment but doesn't allow further distinction within the Shader environment to determine if in Vertex, Fragment, etc. execution models.

SPIRVCallLowering.cpp contains getExecutionModel which implements this by reading the "hlsl.shader" attribute from the passed Function but this path is not always available. Ideally the SPIRVSubtarget could be queried for the current execution model.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions