Skip to content

Conversation

@bashbaug
Copy link
Contributor

fixes #859

Clarifies that the required accuracy for OpFMod and OpFRem is derived from floor and trunc. This is the same behavior as Vulkan - see link.

@bashbaug bashbaug requested a review from alycm January 16, 2023 21:55
Copy link
Contributor

@alycm alycm left a comment

Choose a reason for hiding this comment

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

LGTM.

On the call on 2023-01-17 there was a concern if this wording would cause a problem for implementations that are more precise. The table is explicitly "minimum accuracy" though, so I think it's fine.

There was also mention of a concern that the SPIR-V LLVM translator could be less precise than this, but not sure what to say about it here. I'll add a comment to the original issue.

@bashbaug bashbaug force-pushed the clarify-opfmod-opfrem branch from ed97470 to 82499ce Compare January 24, 2023 16:25
@bashbaug bashbaug marked this pull request as draft January 31, 2023 01:15
@bashbaug
Copy link
Contributor Author

I've converted this to a draft while we determine whether there is a precision issue or not.

@bashbaug
Copy link
Contributor Author

Feedback from discussion on April 11th: it would be best to have a test for the desired behavior first.

@kpet kpet added the needs-cts-coverage The CTS needs to be extended label May 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-cts-coverage The CTS needs to be extended

Projects

None yet

Development

Successfully merging this pull request may close these issues.

SPIR-V Environment Spec does not describe required accuracy for OpFMod and OpFRem

3 participants