Post #2290668
2026-05-08 06:02 UTC
@gfxstrand@social.treehouse.systems It looks at some decorations (like read only). But it doesn't care about the implicit restrict decoration which an external resource has according to spir-v. So it behaves as if you're in OpenCL memory model mode at all times. Likewise there's a question about materializing pointers in the shader, since iirc there's not really any option in shader languages to say "this pointer doesn't alias even though I just materialized it" (other than read only) (or to say the reverse)
Replies (1)
-
@gfxstrand@social.treehouse.systems 2026-05-08 06:06
@dotstdy@mastodon.social Oh, yeah, BDA makes everything tricky. We tried to spec something but when pointers can get materialized out of thin air it can be hard to reason about them. The good news is that unless you’re interleaving access to multiple external pointers (which isn’t common in graphics), we should still be pretty good at sorting it all out.