microsoft / microsoft/DirectXShaderCompiler
[SM 6.8] Reflection for Work Graph nodes plus more general DXIL Library reflection
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 3.7k
- Forks
- 900
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 44
Description
The current D3D12LibraryReflection interfaces do not support exposing function attributes for node shaders. For example, if applications want to setup per-launch mode or per-node overrides they need to be able to identify the launch mode and/or node ID of each node.
Outstanding questions:
- Do we extend the existing library reflection interface to support retrieving those RDAT properties?
- Should we create a more general future-proof API that surfaces RDAT more directly?
Note: more details available in internal work item 94.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing D3D12LibraryReflection interfaces and how they expose RDAT properties for DXIL libraries. Compare the two proposed directions: extending the interface for node-shader function attributes, or exposing RDAT through a more general API. The work is complete when applications can identify each node's launch mode and node ID, with the API choice resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100