-
Notifications
You must be signed in to change notification settings - Fork 282
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
GetDebugMessageLogAMD takes GLint* argument instead of GLenum* #516
Comments
This function will return the following severity levels to parameter GLuint* severities. Refer to specification for details - The GLuint and GLenum are typecasted from unisigned int, so should not be any concerns of conversion from application side. So application will get the Glenum as expected here. The IHV vendors will be returning severity levels as mentioned above. |
This is more of a issue is more in relation to #517. |
I suggest trying to contact Jaakko Konttinen, who is listed as the extension contact. I believe they're still at AMD, 12 years on. I am fairly sure none of the other listed contributors to the extension are still at AMD but if you can't reach the contact, we can ask around inside Khronos to see if anyone at AMD feels ownership over this extension. |
We have approved extension - GL_ARB_ debug_output.txt which has listed these parameters to enum* severities. We have discussed this in working group, and we dont have issues to keep it to GLuint * or change to GLenum* severities. |
To be clear, the WG doesn't have an issue with the GL_AMD_debug_output extension changing from GLuit to GLenum if that's acceptable to AMD. |
Yes, this is acceptable to AMD. |
The function
GetDebugMessageLogAMD
fromGL_AMD_debug_output
is defined as follows:Shouldn't the
severities
argument be of typeGLenum
?This would match every other definition of this function from other extensions.
As they are
typedef
ed as the same type is it possible to change this?The text was updated successfully, but these errors were encountered: