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

A couple of fixes to the GL_QCOM_image_processing2 support #3578

Merged

Conversation

wooyoungqcom
Copy link
Contributor

  1. handle the extension requirements of GL_QCOM_image_processing2
    correctly
  2. add QCOM image processing decorations to ids only once.

1) handle the extension requirements of GL_QCOM_image_processing2
   correctly
2) add QCOM image processing decorations to ids only once.
1) handle the extension requirements of GL_QCOM_image_processing2
   correctly
2) add QCOM image processing decorations to ids only once.
@arcady-lunarg arcady-lunarg added the kokoro:run Trigger Google bot runs label Apr 22, 2024
@kokoro-team kokoro-team removed the kokoro:run Trigger Google bot runs label Apr 22, 2024
Copy link
Contributor

@arcady-lunarg arcady-lunarg left a comment

Choose a reason for hiding this comment

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

Sorry, I should have reviewed the original change more thoroughly, we really shouldn't be checking in expected results with "Validation failed" messages. However, it seems like you still have a "Bad" in your expected results, which is probably something you forgot to add to the appropriate switch statement in SPIRV/doc.cpp.

Test/baseResults/spv.tpipBlockMatchGatherSAD.frag.out Outdated Show resolved Hide resolved
1) handle the extension requirements of GL_QCOM_image_processing2
   correctly
2) add QCOM image processing decorations to ids only once.
@arcady-lunarg arcady-lunarg merged commit a4f8700 into KhronosGroup:main Apr 23, 2024
22 checks passed
@wooyoungqcom wooyoungqcom deleted the GL_QCOM_image_processing2__Fix_1 branch April 25, 2024 08:34
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.

3 participants