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.
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
Helper for robust texture content checking #1055
Helper for robust texture content checking #1055
Changes from all commits
a3176ec
3c41625
fe97977
6c8e6b0
1b010a3
8e2c5c0
13ff652
310cc5b
4404a71
e84848c
048dae5
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shall we throw errors or add assert for this instead of reset it to 0? I'm not sure whether this means bugs in the test cases.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the best would be to actually handle conversion from normal
number
s to subnormal f16, but for the purpose of ULP checks, we don't care about subnormal - we round all subnormal numbers to 0. And generally GPUs don't guarantee results in the subnormal range anyway for a lot of operations. So I think it's unlikely to be a problem.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The old code asserted, but that assertion was hit because we generated small
number
s in color space conversion and then tried to convert to f16.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also recalled that on chromium implementaion, we always convert the White to D50 config (in this case D65 -> D50). This also introduce some precision difference.