KhronosGroup / KhronosGroup/SPIRV-Guide

Add Chapter - Using Debug info

Open
#29 0 comments 0 reactions 1 assignee View on GitHub

@spencer-lunarg is already working on this.

Since Sep 6, 2024.

New Chapter
Dominant language
GLSL
Stars
247
Forks
19
PR merge metrics
No merged PRs in 30d

Description

Things like OpLine, OpSource, NonSemantic.Shader.DebugInfo.100, etc are designed to allow SPIR-V generators to add this information into the SPIR-V and then allow tooling to retrieve this information to help map back information from the SPIR-V

It would be useful to have some examples for both

  • How to add to your SPIR-V (for code generators)
  • How to parse the data out of SPIR-V (for tools)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.