spirv-cross: remove integration - #16099
Open
kenohassler wants to merge 1 commit into
Open
Conversation
spirv-cross is not meant to be used with untrusted input (KhronosGroup/SPIRV-Cross#2413) and maintainers generally do not regard fuzzer bug reports helpful in their threat model (KhronosGroup/SPIRV-Cross#2667). They recommend pre-validating input with spirv-val, which is tested as part of the spirv-tools integration in oss-fuzz. Ergo, remove spirv-cross, as it is only wasting CPU cycles.
|
kenohassler is a new contributor to projects/spirv-cross. The PR must be approved by known contributors before it can be merged. The past contributors are: hunsche |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
spirv-cross is not meant to be used with untrusted input (KhronosGroup/SPIRV-Cross#2413) and maintainers generally do not regard fuzzer bug reports helpful in their threat model (KhronosGroup/SPIRV-Cross#2667).
They recommend pre-validating input with
spirv-val, which is tested as part of the spirv-tools integration in oss-fuzz. Ergo, remove spirv-cross integration, as it is only wasting CPU cycles.