Skip to content
This repository has been archived by the owner on Dec 8, 2022. It is now read-only.

disallow ImageRead, ImageWrite, ImageFetch with ConstOffset #53

Open
dneto0 opened this issue Dec 10, 2020 · 1 comment
Open

disallow ImageRead, ImageWrite, ImageFetch with ConstOffset #53

dneto0 opened this issue Dec 10, 2020 · 1 comment

Comments

@dneto0
Copy link
Contributor

dneto0 commented Dec 10, 2020

In WGSL, textureLoad, textureStore do not have overloads with an offset parameter.

See also https://bugs.chromium.org/p/tint/issues/detail?id=408

@dneto0
Copy link
Contributor Author

dneto0 commented Dec 17, 2020

Vulkan permits use of ConstOffset with ImageFetch.

I suspect there is a missing rule to ban ConstOffset with ImageRead, ImageWrite.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant