You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I acknowledge that storing a buffer binding into a buffer is ridiculous and not in spec. However, it should probably give an error, not sigsegv.
Description
Encountered a SIGSEGV running dxc on a shader when trying to find if there's any existing bugs in having structs contain buffers when compiled to spir-v. (this issue is a different error than the one I was looking for, this one happens when outputting dxil)
noahwhygodwhy
changed the title
SIGSEGV when storing struct with buffer that was loaded specifically from array of buffers
SIGSEGV when storing struct with buffer that was picked specifically from array of buffers
Apr 28, 2025
Preamble
I acknowledge that storing a buffer binding into a buffer is ridiculous and not in spec. However, it should probably give an error, not sigsegv.
Description
Encountered a SIGSEGV running dxc on a shader when trying to find if there's any existing bugs in having structs contain buffers when compiled to spir-v. (this issue is a different error than the one I was looking for, this one happens when outputting dxil)
Steps to Reproduce
https://godbolt.org/z/8jhTebWY5
When the buffer buff3 is put into the struct and then stored, the compiler outputs a seemingly correct error.
However when a selection from the buff2 buffer array is put into the struct, and then stored, it crashes.
Behavior is identical for buff2[] and buff3 when outputting spirv. It only crashes for dxil.
Actual Behavior
SIGSEGV code 139
Environment
The text was updated successfully, but these errors were encountered: