Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove undefined behavior for ray queries #6761

Open
4 tasks
Vecvec opened this issue Dec 16, 2024 · 0 comments
Open
4 tasks

Remove undefined behavior for ray queries #6761

Vecvec opened this issue Dec 16, 2024 · 0 comments
Labels
api: vulkan Issues with Vulkan area: correctness We're behaving incorrectly area: validation Issues related to validation, diagnostics, and error handling feature: raytracing Issues with the Ray Tracing Native Feature naga Shader Translator type: bug Something isn't working

Comments

@Vecvec
Copy link
Contributor

Vecvec commented Dec 16, 2024

Is your feature request related to a problem? Please describe.
Currently the ray queries have lots of undefined behavior from the spirv spec that should be removed

Describe the solution you'd like
Prevent the undefined behaviour

Describe alternatives you've considered
Not remove it.

Additional context
also see #6731 for some details of what can happen.
current undefined behavior:

  • Anytime a ray misses and rayQueryGet*Intersection is called - [spirv] Stop naga causing undefined behavior in rayQueryGet*Intersection #6752
  • Calling rayQueryGetCommittedIntersection or rayQueryGetCandidateIntersection when rayQueryProceed has not been called called on this ray query since it was initialized (or if the ray query has not been previously initialized).
  • Calling rayQueryGetCommittedIntersection when rayQueryProceed's latest return on this ray query is considered Candidate (and the other way round too).
  • Calling rayQueryProceed when rayQueryInitialize has not previously been called on this ray query.
@cwfitzgerald cwfitzgerald added type: bug Something isn't working area: validation Issues related to validation, diagnostics, and error handling area: correctness We're behaving incorrectly api: vulkan Issues with Vulkan naga Shader Translator feature: raytracing Issues with the Ray Tracing Native Feature labels Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: vulkan Issues with Vulkan area: correctness We're behaving incorrectly area: validation Issues related to validation, diagnostics, and error handling feature: raytracing Issues with the Ray Tracing Native Feature naga Shader Translator type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants