Originally posted by Dandel
View Post
Behaviour when passing NaN to an OpenGL function is undefined IIRC, as long as the implementation does not crash, so I would argue that returning GL_INVALID_VALUE is perfectly legal and is probably the "most correct" behaviour.
The winehq bug ticket has some discussion about a patch to intercept NaN values before they get to the driver; seems like the patch works in some place but not others, which suggests that the it is not blocking NaN under all conditions.
Comment