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

spirv-val: Add support for SPV_AMD_shader_image_load_store_lod #3186

Merged

Conversation

samuelig
Copy link
Contributor

According to SPV_AMD_shader_image_load_store_lod spec, Lod operand is
valid with OpImageRead, OpImageWrite, or OpImageSparseRead if the
extension is enabled.

@claassistantio
Copy link

claassistantio commented Feb 12, 2020

CLA assistant check
All committers have signed the CLA.

Copy link
Contributor

@alan-baker alan-baker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please also add tests for sparse read.

source/val/validation_state.h Outdated Show resolved Hide resolved
According to SPV_AMD_shader_image_load_store_lod spec, Lod operand is
valid with OpImageRead, OpImageWrite, or OpImageSparseRead if the
extension is enabled.
@samuelig samuelig force-pushed the SPV_AMD_shader_image_load_store_lod branch from a2845c2 to 0bdf278 Compare February 14, 2020 07:42
@samuelig
Copy link
Contributor Author

CI-shaderc-smoketest check is failing because glslang expects a validation failure on a SPV_AMD_shader_image_load_store_lod test . I have a fix here.

Should I land glslang fix first for review? Or land this first and then the glslang fix? Which is the procedure for this case?

@samuelig
Copy link
Contributor Author

CI-shaderc-smoketest check is failing because glslang expects a validation failure on a SPV_AMD_shader_image_load_store_lod test . I have a fix here.

Should I land glslang fix first for review? Or land this first and then the glslang fix? Which is the procedure for this case?

Glslang pull request: KhronosGroup/glslang#2086

@alan-baker alan-baker merged commit 4d912f4 into KhronosGroup:master Feb 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants