archive/blender-archive
Archived
1
1
Fork 0
Code Pull Requests Packages Activity
This repository has been archived on 2023-10-09. You can view files and clone it, but cannot push or open issues or pull requests.
Files
6bf9c8ac8918a6656c20cca2c08f20b38e90980c
blender-archive/source/blender/gpu/intern/gpu_debug.c

611 lines
22 KiB
C
Raw Normal View History

Debug GPU functionality from soc-viewport_fx by Jason Wilkins patch number D706 with changes: - WITH_GPU_DEBUG just creates a debug context (and enables the debug messaging system functions) but leaves the checks we had intact. Old patch added the debug functionality only if we had the flag on to save some performance. Rationale here is that we might not want to recompile blender just to get the extra information, and having users start blender with a -d flag to get the extra information is also useful for bug reports. Those checks already existed and most expensive ones are hidden behind a debug mode check so performance should not be that bad. - Did some cleanup of existing functionality: When things go wrong blender side, just print the error, don't check for GL errors first. - Did not port changes needed for GLES to regular glew.h - Got rid of duplicate or very similar new functionality. Generally, code is more moving things around/cleanup and should work exactly as before apart from the debug context, so it's safe to add even now. It also provides a nice substitute function for glu error descriptions
2015-02-16 21:19:12 +01:00
/*
* ***** BEGIN GPL LICENSE BLOCK *****
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License
* as published by the Free Software Foundation; either version 2
* of the License, or (at your option) any later version.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program; if not, write to the Free Software Foundation,
* Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
*
* The Original Code is Copyright (C) 2005 Blender Foundation.
* All rights reserved.
*
* The Original Code is: all of this file.
*
* Contributor(s): Brecht Van Lommel, Jason Wilkins.
*
* ***** END GPL LICENSE BLOCK *****
*/
Cleanup
2015-03-16 11:46:20 +11:00
/** \file source/blender/gpu/intern/gpu_debug.c
Debug GPU functionality from soc-viewport_fx by Jason Wilkins patch number D706 with changes: - WITH_GPU_DEBUG just creates a debug context (and enables the debug messaging system functions) but leaves the checks we had intact. Old patch added the debug functionality only if we had the flag on to save some performance. Rationale here is that we might not want to recompile blender just to get the extra information, and having users start blender with a -d flag to get the extra information is also useful for bug reports. Those checks already existed and most expensive ones are hidden behind a debug mode check so performance should not be that bad. - Did some cleanup of existing functionality: When things go wrong blender side, just print the error, don't check for GL errors first. - Did not port changes needed for GLES to regular glew.h - Got rid of duplicate or very similar new functionality. Generally, code is more moving things around/cleanup and should work exactly as before apart from the debug context, so it's safe to add even now. It also provides a nice substitute function for glu error descriptions
2015-02-16 21:19:12 +01:00
* \ingroup gpu
*/
fix #includes for GPU debug Can now build release and debug. Close to final version in master (which took several commits).
2016-08-16 17:14:42 -04:00
#include "BLI_utildefines.h"
Debug GPU functionality from soc-viewport_fx by Jason Wilkins patch number D706 with changes: - WITH_GPU_DEBUG just creates a debug context (and enables the debug messaging system functions) but leaves the checks we had intact. Old patch added the debug functionality only if we had the flag on to save some performance. Rationale here is that we might not want to recompile blender just to get the extra information, and having users start blender with a -d flag to get the extra information is also useful for bug reports. Those checks already existed and most expensive ones are hidden behind a debug mode check so performance should not be that bad. - Did some cleanup of existing functionality: When things go wrong blender side, just print the error, don't check for GL errors first. - Did not port changes needed for GLES to regular glew.h - Got rid of duplicate or very similar new functionality. Generally, code is more moving things around/cleanup and should work exactly as before apart from the debug context, so it's safe to add even now. It also provides a nice substitute function for glu error descriptions
2015-02-16 21:19:12 +01:00
#include "BLI_sys_types.h"
fix #includes for GPU debug Can now build release and debug. Close to final version in master (which took several commits).
2016-08-16 17:14:42 -04:00
#include "BLI_system.h"
Debug GPU functionality from soc-viewport_fx by Jason Wilkins patch number D706 with changes: - WITH_GPU_DEBUG just creates a debug context (and enables the debug messaging system functions) but leaves the checks we had intact. Old patch added the debug functionality only if we had the flag on to save some performance. Rationale here is that we might not want to recompile blender just to get the extra information, and having users start blender with a -d flag to get the extra information is also useful for bug reports. Those checks already existed and most expensive ones are hidden behind a debug mode check so performance should not be that bad. - Did some cleanup of existing functionality: When things go wrong blender side, just print the error, don't check for GL errors first. - Did not port changes needed for GLES to regular glew.h - Got rid of duplicate or very similar new functionality. Generally, code is more moving things around/cleanup and should work exactly as before apart from the debug context, so it's safe to add even now. It also provides a nice substitute function for glu error descriptions
2015-02-16 21:19:12 +01:00
#include "BKE_global.h"
#include "GPU_glew.h"
#include "GPU_debug.h"
#include "intern/gpu_private.h"
#include <stdio.h>
Fix compilation error after recent GPU debug changes
2015-02-23 18:09:28 +05:00
#include <stdlib.h>
Debug GPU functionality from soc-viewport_fx by Jason Wilkins patch number D706 with changes: - WITH_GPU_DEBUG just creates a debug context (and enables the debug messaging system functions) but leaves the checks we had intact. Old patch added the debug functionality only if we had the flag on to save some performance. Rationale here is that we might not want to recompile blender just to get the extra information, and having users start blender with a -d flag to get the extra information is also useful for bug reports. Those checks already existed and most expensive ones are hidden behind a debug mode check so performance should not be that bad. - Did some cleanup of existing functionality: When things go wrong blender side, just print the error, don't check for GL errors first. - Did not port changes needed for GLES to regular glew.h - Got rid of duplicate or very similar new functionality. Generally, code is more moving things around/cleanup and should work exactly as before apart from the debug context, so it's safe to add even now. It also provides a nice substitute function for glu error descriptions
2015-02-16 21:19:12 +01:00
#include <string.h>
OpenGL: simplify debug, use only newer features Drop SciTech support & workarounds for WinCE and OpenGL ES. AMD_debug_output is still in the code but disabled. Once I verify the newer extensions are available on all the GPU + OS combos we support we can delete this disabled code.
2016-11-12 17:18:13 -06:00
/* control whether we use older AMD_debug_output extension, or just the newer extensions
* TODO(merwin): determine whether all supported GPU + OS combos have newer extensions */
#define LEGACY_DEBUG 0
Debug GPU functionality from soc-viewport_fx by Jason Wilkins patch number D706 with changes: - WITH_GPU_DEBUG just creates a debug context (and enables the debug messaging system functions) but leaves the checks we had intact. Old patch added the debug functionality only if we had the flag on to save some performance. Rationale here is that we might not want to recompile blender just to get the extra information, and having users start blender with a -d flag to get the extra information is also useful for bug reports. Those checks already existed and most expensive ones are hidden behind a debug mode check so performance should not be that bad. - Did some cleanup of existing functionality: When things go wrong blender side, just print the error, don't check for GL errors first. - Did not port changes needed for GLES to regular glew.h - Got rid of duplicate or very similar new functionality. Generally, code is more moving things around/cleanup and should work exactly as before apart from the debug context, so it's safe to add even now. It also provides a nice substitute function for glu error descriptions
2015-02-16 21:19:12 +01:00
OpenGL: simplify debug, use only newer features Drop SciTech support & workarounds for WinCE and OpenGL ES. AMD_debug_output is still in the code but disabled. Once I verify the newer extensions are available on all the GPU + OS combos we support we can delete this disabled code.
2016-11-12 17:18:13 -06:00
/* Debug callbacks need the same calling convention as OpenGL functions. */
#if defined(_WIN32)
Debug GPU functionality from soc-viewport_fx by Jason Wilkins patch number D706 with changes: - WITH_GPU_DEBUG just creates a debug context (and enables the debug messaging system functions) but leaves the checks we had intact. Old patch added the debug functionality only if we had the flag on to save some performance. Rationale here is that we might not want to recompile blender just to get the extra information, and having users start blender with a -d flag to get the extra information is also useful for bug reports. Those checks already existed and most expensive ones are hidden behind a debug mode check so performance should not be that bad. - Did some cleanup of existing functionality: When things go wrong blender side, just print the error, don't check for GL errors first. - Did not port changes needed for GLES to regular glew.h - Got rid of duplicate or very similar new functionality. Generally, code is more moving things around/cleanup and should work exactly as before apart from the debug context, so it's safe to add even now. It also provides a nice substitute function for glu error descriptions
2015-02-16 21:19:12 +01:00
# define APIENTRY __stdcall
#else
# define APIENTRY
#endif
OpenGL: enhance debug output When running blender --debug-gpu Display which debug facilities are available. One of these, in order of preference: - OpenGL 4.3 - KHR_debug - ARB_debug_output - AMD_debug_output All messages are logged now, not just errors. Will probably turn some of these off later. GL_DEBUG_OUTPUT_SYNCHRONOUS lets us break on errors and backtrace to the exact trouble spot. Callers of GPU_string_marker no longer pass in a message length, just the message itself (null terminated). Apple provides no GL debug logging features.
2016-08-09 01:29:58 -04:00
static const char* source_name(GLenum source)
{
switch (source) {
case GL_DEBUG_SOURCE_API: return "API";
case GL_DEBUG_SOURCE_WINDOW_SYSTEM: return "window system";
case GL_DEBUG_SOURCE_SHADER_COMPILER: return "shader compiler";
case GL_DEBUG_SOURCE_THIRD_PARTY: return "3rd party";
case GL_DEBUG_SOURCE_APPLICATION: return "application";
case GL_DEBUG_SOURCE_OTHER: return "other";
default: return "???";
}
}
static const char* message_type_name(GLenum message)
{
switch (message) {
case GL_DEBUG_TYPE_ERROR: return "error";
case GL_DEBUG_TYPE_DEPRECATED_BEHAVIOR: return "deprecated behavior";
case GL_DEBUG_TYPE_UNDEFINED_BEHAVIOR: return "undefined behavior";
case GL_DEBUG_TYPE_PORTABILITY: return "portability";
case GL_DEBUG_TYPE_PERFORMANCE: return "performance";
case GL_DEBUG_TYPE_OTHER: return "other";
case GL_DEBUG_TYPE_MARKER: return "marker"; /* KHR has this, ARB does not */
default: return "???";
}
}
Quiet warning with arg types
2015-08-25 17:27:18 +10:00
static void APIENTRY gpu_debug_proc(
GLenum source, GLenum type, GLuint UNUSED(id),
OpenGL: enhance debug output When running blender --debug-gpu Display which debug facilities are available. One of these, in order of preference: - OpenGL 4.3 - KHR_debug - ARB_debug_output - AMD_debug_output All messages are logged now, not just errors. Will probably turn some of these off later. GL_DEBUG_OUTPUT_SYNCHRONOUS lets us break on errors and backtrace to the exact trouble spot. Callers of GPU_string_marker no longer pass in a message length, just the message itself (null terminated). Apple provides no GL debug logging features.
2016-08-09 01:29:58 -04:00
GLenum severity, GLsizei UNUSED(length),
Revert "Fix compile error in gpu_debug (incompatible-pointer-type)." This reverts commit 75cfc81ec39ac9953f25eb0ae5f9e70d3c24ee7e.
2016-01-17 13:19:14 +11:00
const GLchar *message, const GLvoid *UNUSED(userParm))
Debug GPU functionality from soc-viewport_fx by Jason Wilkins patch number D706 with changes: - WITH_GPU_DEBUG just creates a debug context (and enables the debug messaging system functions) but leaves the checks we had intact. Old patch added the debug functionality only if we had the flag on to save some performance. Rationale here is that we might not want to recompile blender just to get the extra information, and having users start blender with a -d flag to get the extra information is also useful for bug reports. Those checks already existed and most expensive ones are hidden behind a debug mode check so performance should not be that bad. - Did some cleanup of existing functionality: When things go wrong blender side, just print the error, don't check for GL errors first. - Did not port changes needed for GLES to regular glew.h - Got rid of duplicate or very similar new functionality. Generally, code is more moving things around/cleanup and should work exactly as before apart from the debug context, so it's safe to add even now. It also provides a nice substitute function for glu error descriptions
2015-02-16 21:19:12 +01:00
{
OpenGL: backtrace on errors (--debug-gpu) Backtrace so we can pinpoint where the GL error came from. Then fflush on severe errors in case it's severe enough to crash Blender.
2016-08-15 04:00:59 -04:00
bool backtrace = false;
OpenGL: enhance debug output When running blender --debug-gpu Display which debug facilities are available. One of these, in order of preference: - OpenGL 4.3 - KHR_debug - ARB_debug_output - AMD_debug_output All messages are logged now, not just errors. Will probably turn some of these off later. GL_DEBUG_OUTPUT_SYNCHRONOUS lets us break on errors and backtrace to the exact trouble spot. Callers of GPU_string_marker no longer pass in a message length, just the message itself (null terminated). Apple provides no GL debug logging features.
2016-08-09 01:29:58 -04:00
switch (severity) {
case GL_DEBUG_SEVERITY_HIGH:
OpenGL: backtrace on errors (--debug-gpu) Backtrace so we can pinpoint where the GL error came from. Then fflush on severe errors in case it's severe enough to crash Blender.
2016-08-15 04:00:59 -04:00
backtrace = true;
/* fall through */
OpenGL: enhance debug output When running blender --debug-gpu Display which debug facilities are available. One of these, in order of preference: - OpenGL 4.3 - KHR_debug - ARB_debug_output - AMD_debug_output All messages are logged now, not just errors. Will probably turn some of these off later. GL_DEBUG_OUTPUT_SYNCHRONOUS lets us break on errors and backtrace to the exact trouble spot. Callers of GPU_string_marker no longer pass in a message length, just the message itself (null terminated). Apple provides no GL debug logging features.
2016-08-09 01:29:58 -04:00
case GL_DEBUG_SEVERITY_MEDIUM:
case GL_DEBUG_SEVERITY_LOW:
case GL_DEBUG_SEVERITY_NOTIFICATION: /* KHR has this, ARB does not */
fprintf(stderr, "GL %s %s: %s\n", source_name(source), message_type_name(type), message);
OpenGL: backtrace on errors (--debug-gpu) Backtrace so we can pinpoint where the GL error came from. Then fflush on severe errors in case it's severe enough to crash Blender.
2016-08-15 04:00:59 -04:00
}
if (backtrace) {
BLI_system_backtrace(stderr);
fflush(stderr);
Filter the debug callback to only report errors unless debug value is 20. stderr was getting flooded with too many error messages, most of which were not really relevant.
2015-07-20 14:37:22 +02:00
}
Debug GPU functionality from soc-viewport_fx by Jason Wilkins patch number D706 with changes: - WITH_GPU_DEBUG just creates a debug context (and enables the debug messaging system functions) but leaves the checks we had intact. Old patch added the debug functionality only if we had the flag on to save some performance. Rationale here is that we might not want to recompile blender just to get the extra information, and having users start blender with a -d flag to get the extra information is also useful for bug reports. Those checks already existed and most expensive ones are hidden behind a debug mode check so performance should not be that bad. - Did some cleanup of existing functionality: When things go wrong blender side, just print the error, don't check for GL errors first. - Did not port changes needed for GLES to regular glew.h - Got rid of duplicate or very similar new functionality. Generally, code is more moving things around/cleanup and should work exactly as before apart from the debug context, so it's safe to add even now. It also provides a nice substitute function for glu error descriptions
2015-02-16 21:19:12 +01:00
}
OpenGL: simplify debug, use only newer features Drop SciTech support & workarounds for WinCE and OpenGL ES. AMD_debug_output is still in the code but disabled. Once I verify the newer extensions are available on all the GPU + OS combos we support we can delete this disabled code.
2016-11-12 17:18:13 -06:00
#if LEGACY_DEBUG
static const char* category_name_amd(GLenum category)
{
switch (category) {
case GL_DEBUG_CATEGORY_API_ERROR_AMD: return "API error";
case GL_DEBUG_CATEGORY_WINDOW_SYSTEM_AMD: return "window system";
case GL_DEBUG_CATEGORY_DEPRECATION_AMD: return "deprecated behavior";
case GL_DEBUG_CATEGORY_UNDEFINED_BEHAVIOR_AMD: return "undefined behavior";
case GL_DEBUG_CATEGORY_PERFORMANCE_AMD: return "performance";
case GL_DEBUG_CATEGORY_SHADER_COMPILER_AMD: return "shader compiler";
case GL_DEBUG_CATEGORY_APPLICATION_AMD: return "application";
case GL_DEBUG_CATEGORY_OTHER_AMD: return "other";
default: return "???";
}
}
Debug GPU functionality from soc-viewport_fx by Jason Wilkins patch number D706 with changes: - WITH_GPU_DEBUG just creates a debug context (and enables the debug messaging system functions) but leaves the checks we had intact. Old patch added the debug functionality only if we had the flag on to save some performance. Rationale here is that we might not want to recompile blender just to get the extra information, and having users start blender with a -d flag to get the extra information is also useful for bug reports. Those checks already existed and most expensive ones are hidden behind a debug mode check so performance should not be that bad. - Did some cleanup of existing functionality: When things go wrong blender side, just print the error, don't check for GL errors first. - Did not port changes needed for GLES to regular glew.h - Got rid of duplicate or very similar new functionality. Generally, code is more moving things around/cleanup and should work exactly as before apart from the debug context, so it's safe to add even now. It also provides a nice substitute function for glu error descriptions
2015-02-16 21:19:12 +01:00
Quiet warning with arg types
2015-08-25 17:27:18 +10:00
static void APIENTRY gpu_debug_proc_amd(
OpenGL: enhance debug output When running blender --debug-gpu Display which debug facilities are available. One of these, in order of preference: - OpenGL 4.3 - KHR_debug - ARB_debug_output - AMD_debug_output All messages are logged now, not just errors. Will probably turn some of these off later. GL_DEBUG_OUTPUT_SYNCHRONOUS lets us break on errors and backtrace to the exact trouble spot. Callers of GPU_string_marker no longer pass in a message length, just the message itself (null terminated). Apple provides no GL debug logging features.
2016-08-09 01:29:58 -04:00
GLuint UNUSED(id), GLenum category,
GLenum severity, GLsizei UNUSED(length),
Quiet warning with arg types
2015-08-25 17:27:18 +10:00
const GLchar *message, GLvoid *UNUSED(userParm))
Debug GPU functionality from soc-viewport_fx by Jason Wilkins patch number D706 with changes: - WITH_GPU_DEBUG just creates a debug context (and enables the debug messaging system functions) but leaves the checks we had intact. Old patch added the debug functionality only if we had the flag on to save some performance. Rationale here is that we might not want to recompile blender just to get the extra information, and having users start blender with a -d flag to get the extra information is also useful for bug reports. Those checks already existed and most expensive ones are hidden behind a debug mode check so performance should not be that bad. - Did some cleanup of existing functionality: When things go wrong blender side, just print the error, don't check for GL errors first. - Did not port changes needed for GLES to regular glew.h - Got rid of duplicate or very similar new functionality. Generally, code is more moving things around/cleanup and should work exactly as before apart from the debug context, so it's safe to add even now. It also provides a nice substitute function for glu error descriptions
2015-02-16 21:19:12 +01:00
{
OpenGL: backtrace on errors (--debug-gpu) Backtrace so we can pinpoint where the GL error came from. Then fflush on severe errors in case it's severe enough to crash Blender.
2016-08-15 04:00:59 -04:00
bool backtrace = false;
OpenGL: enhance debug output When running blender --debug-gpu Display which debug facilities are available. One of these, in order of preference: - OpenGL 4.3 - KHR_debug - ARB_debug_output - AMD_debug_output All messages are logged now, not just errors. Will probably turn some of these off later. GL_DEBUG_OUTPUT_SYNCHRONOUS lets us break on errors and backtrace to the exact trouble spot. Callers of GPU_string_marker no longer pass in a message length, just the message itself (null terminated). Apple provides no GL debug logging features.
2016-08-09 01:29:58 -04:00
switch (severity) {
case GL_DEBUG_SEVERITY_HIGH:
OpenGL: backtrace on errors (--debug-gpu) Backtrace so we can pinpoint where the GL error came from. Then fflush on severe errors in case it's severe enough to crash Blender.
2016-08-15 04:00:59 -04:00
backtrace = true;
/* fall through */
OpenGL: enhance debug output When running blender --debug-gpu Display which debug facilities are available. One of these, in order of preference: - OpenGL 4.3 - KHR_debug - ARB_debug_output - AMD_debug_output All messages are logged now, not just errors. Will probably turn some of these off later. GL_DEBUG_OUTPUT_SYNCHRONOUS lets us break on errors and backtrace to the exact trouble spot. Callers of GPU_string_marker no longer pass in a message length, just the message itself (null terminated). Apple provides no GL debug logging features.
2016-08-09 01:29:58 -04:00
case GL_DEBUG_SEVERITY_MEDIUM:
case GL_DEBUG_SEVERITY_LOW:
fprintf(stderr, "GL %s: %s\n", category_name_amd(category), message);
OpenGL: backtrace on errors (--debug-gpu) Backtrace so we can pinpoint where the GL error came from. Then fflush on severe errors in case it's severe enough to crash Blender.
2016-08-15 04:00:59 -04:00
}
if (backtrace) {
BLI_system_backtrace(stderr);
fflush(stderr);
OpenGL: enhance debug output When running blender --debug-gpu Display which debug facilities are available. One of these, in order of preference: - OpenGL 4.3 - KHR_debug - ARB_debug_output - AMD_debug_output All messages are logged now, not just errors. Will probably turn some of these off later. GL_DEBUG_OUTPUT_SYNCHRONOUS lets us break on errors and backtrace to the exact trouble spot. Callers of GPU_string_marker no longer pass in a message length, just the message itself (null terminated). Apple provides no GL debug logging features.
2016-08-09 01:29:58 -04:00
}
Debug GPU functionality from soc-viewport_fx by Jason Wilkins patch number D706 with changes: - WITH_GPU_DEBUG just creates a debug context (and enables the debug messaging system functions) but leaves the checks we had intact. Old patch added the debug functionality only if we had the flag on to save some performance. Rationale here is that we might not want to recompile blender just to get the extra information, and having users start blender with a -d flag to get the extra information is also useful for bug reports. Those checks already existed and most expensive ones are hidden behind a debug mode check so performance should not be that bad. - Did some cleanup of existing functionality: When things go wrong blender side, just print the error, don't check for GL errors first. - Did not port changes needed for GLES to regular glew.h - Got rid of duplicate or very similar new functionality. Generally, code is more moving things around/cleanup and should work exactly as before apart from the debug context, so it's safe to add even now. It also provides a nice substitute function for glu error descriptions
2015-02-16 21:19:12 +01:00
}
OpenGL: simplify debug, use only newer features Drop SciTech support & workarounds for WinCE and OpenGL ES. AMD_debug_output is still in the code but disabled. Once I verify the newer extensions are available on all the GPU + OS combos we support we can delete this disabled code.
2016-11-12 17:18:13 -06:00
#endif /* LEGACY_DEBUG */
Debug GPU functionality from soc-viewport_fx by Jason Wilkins patch number D706 with changes: - WITH_GPU_DEBUG just creates a debug context (and enables the debug messaging system functions) but leaves the checks we had intact. Old patch added the debug functionality only if we had the flag on to save some performance. Rationale here is that we might not want to recompile blender just to get the extra information, and having users start blender with a -d flag to get the extra information is also useful for bug reports. Those checks already existed and most expensive ones are hidden behind a debug mode check so performance should not be that bad. - Did some cleanup of existing functionality: When things go wrong blender side, just print the error, don't check for GL errors first. - Did not port changes needed for GLES to regular glew.h - Got rid of duplicate or very similar new functionality. Generally, code is more moving things around/cleanup and should work exactly as before apart from the debug context, so it's safe to add even now. It also provides a nice substitute function for glu error descriptions
2015-02-16 21:19:12 +01:00
#undef APIENTRY
void gpu_debug_init(void)
{
const char success[] = "Successfully hooked OpenGL debug callback.";
OpenGL: simplify debug, use only newer features Drop SciTech support & workarounds for WinCE and OpenGL ES. AMD_debug_output is still in the code but disabled. Once I verify the newer extensions are available on all the GPU + OS combos we support we can delete this disabled code.
2016-11-12 17:18:13 -06:00
if (GLEW_VERSION_4_3 || GLEW_KHR_debug) {
fprintf(stderr, "Using %s\n", GLEW_VERSION_4_3 ? "OpenGL 4.3 debug facilities" : "KHR_debug extension");
OpenGL: enhance debug output When running blender --debug-gpu Display which debug facilities are available. One of these, in order of preference: - OpenGL 4.3 - KHR_debug - ARB_debug_output - AMD_debug_output All messages are logged now, not just errors. Will probably turn some of these off later. GL_DEBUG_OUTPUT_SYNCHRONOUS lets us break on errors and backtrace to the exact trouble spot. Callers of GPU_string_marker no longer pass in a message length, just the message itself (null terminated). Apple provides no GL debug logging features.
2016-08-09 01:29:58 -04:00
glEnable(GL_DEBUG_OUTPUT);
glEnable(GL_DEBUG_OUTPUT_SYNCHRONOUS);
Cleanup some warnings
2016-03-15 14:16:16 +05:00
glDebugMessageCallback((GLDEBUGPROC)gpu_debug_proc, mxGetCurrentContext());
Cleanup: style Also use gcc style file:line: syntax for errors.
2015-10-17 02:46:38 +11:00
glDebugMessageControl(GL_DONT_CARE, GL_DONT_CARE, GL_DONT_CARE, 0, NULL, GL_TRUE);
OpenGL: enhance debug output When running blender --debug-gpu Display which debug facilities are available. One of these, in order of preference: - OpenGL 4.3 - KHR_debug - ARB_debug_output - AMD_debug_output All messages are logged now, not just errors. Will probably turn some of these off later. GL_DEBUG_OUTPUT_SYNCHRONOUS lets us break on errors and backtrace to the exact trouble spot. Callers of GPU_string_marker no longer pass in a message length, just the message itself (null terminated). Apple provides no GL debug logging features.
2016-08-09 01:29:58 -04:00
GPU_string_marker(success);
Debug GPU functionality from soc-viewport_fx by Jason Wilkins patch number D706 with changes: - WITH_GPU_DEBUG just creates a debug context (and enables the debug messaging system functions) but leaves the checks we had intact. Old patch added the debug functionality only if we had the flag on to save some performance. Rationale here is that we might not want to recompile blender just to get the extra information, and having users start blender with a -d flag to get the extra information is also useful for bug reports. Those checks already existed and most expensive ones are hidden behind a debug mode check so performance should not be that bad. - Did some cleanup of existing functionality: When things go wrong blender side, just print the error, don't check for GL errors first. - Did not port changes needed for GLES to regular glew.h - Got rid of duplicate or very similar new functionality. Generally, code is more moving things around/cleanup and should work exactly as before apart from the debug context, so it's safe to add even now. It also provides a nice substitute function for glu error descriptions
2015-02-16 21:19:12 +01:00
}
OpenGL: simplify debug, use only newer features Drop SciTech support & workarounds for WinCE and OpenGL ES. AMD_debug_output is still in the code but disabled. Once I verify the newer extensions are available on all the GPU + OS combos we support we can delete this disabled code.
2016-11-12 17:18:13 -06:00
else if (GLEW_ARB_debug_output) {
OpenGL: enhance debug output When running blender --debug-gpu Display which debug facilities are available. One of these, in order of preference: - OpenGL 4.3 - KHR_debug - ARB_debug_output - AMD_debug_output All messages are logged now, not just errors. Will probably turn some of these off later. GL_DEBUG_OUTPUT_SYNCHRONOUS lets us break on errors and backtrace to the exact trouble spot. Callers of GPU_string_marker no longer pass in a message length, just the message itself (null terminated). Apple provides no GL debug logging features.
2016-08-09 01:29:58 -04:00
fprintf(stderr, "Using ARB_debug_output extension\n");
glEnable(GL_DEBUG_OUTPUT_SYNCHRONOUS);
Cleanup some warnings
2016-03-15 14:16:16 +05:00
glDebugMessageCallbackARB((GLDEBUGPROCARB)gpu_debug_proc, mxGetCurrentContext());
Debug GPU functionality from soc-viewport_fx by Jason Wilkins patch number D706 with changes: - WITH_GPU_DEBUG just creates a debug context (and enables the debug messaging system functions) but leaves the checks we had intact. Old patch added the debug functionality only if we had the flag on to save some performance. Rationale here is that we might not want to recompile blender just to get the extra information, and having users start blender with a -d flag to get the extra information is also useful for bug reports. Those checks already existed and most expensive ones are hidden behind a debug mode check so performance should not be that bad. - Did some cleanup of existing functionality: When things go wrong blender side, just print the error, don't check for GL errors first. - Did not port changes needed for GLES to regular glew.h - Got rid of duplicate or very similar new functionality. Generally, code is more moving things around/cleanup and should work exactly as before apart from the debug context, so it's safe to add even now. It also provides a nice substitute function for glu error descriptions
2015-02-16 21:19:12 +01:00
glDebugMessageControlARB(GL_DONT_CARE, GL_DONT_CARE, GL_DONT_CARE, 0, NULL, GL_TRUE);
OpenGL: enhance debug output When running blender --debug-gpu Display which debug facilities are available. One of these, in order of preference: - OpenGL 4.3 - KHR_debug - ARB_debug_output - AMD_debug_output All messages are logged now, not just errors. Will probably turn some of these off later. GL_DEBUG_OUTPUT_SYNCHRONOUS lets us break on errors and backtrace to the exact trouble spot. Callers of GPU_string_marker no longer pass in a message length, just the message itself (null terminated). Apple provides no GL debug logging features.
2016-08-09 01:29:58 -04:00
GPU_string_marker(success);
Debug GPU functionality from soc-viewport_fx by Jason Wilkins patch number D706 with changes: - WITH_GPU_DEBUG just creates a debug context (and enables the debug messaging system functions) but leaves the checks we had intact. Old patch added the debug functionality only if we had the flag on to save some performance. Rationale here is that we might not want to recompile blender just to get the extra information, and having users start blender with a -d flag to get the extra information is also useful for bug reports. Those checks already existed and most expensive ones are hidden behind a debug mode check so performance should not be that bad. - Did some cleanup of existing functionality: When things go wrong blender side, just print the error, don't check for GL errors first. - Did not port changes needed for GLES to regular glew.h - Got rid of duplicate or very similar new functionality. Generally, code is more moving things around/cleanup and should work exactly as before apart from the debug context, so it's safe to add even now. It also provides a nice substitute function for glu error descriptions
2015-02-16 21:19:12 +01:00
}
OpenGL: simplify debug, use only newer features Drop SciTech support & workarounds for WinCE and OpenGL ES. AMD_debug_output is still in the code but disabled. Once I verify the newer extensions are available on all the GPU + OS combos we support we can delete this disabled code.
2016-11-12 17:18:13 -06:00
#if LEGACY_DEBUG
else if (GLEW_AMD_debug_output) {
OpenGL: enhance debug output When running blender --debug-gpu Display which debug facilities are available. One of these, in order of preference: - OpenGL 4.3 - KHR_debug - ARB_debug_output - AMD_debug_output All messages are logged now, not just errors. Will probably turn some of these off later. GL_DEBUG_OUTPUT_SYNCHRONOUS lets us break on errors and backtrace to the exact trouble spot. Callers of GPU_string_marker no longer pass in a message length, just the message itself (null terminated). Apple provides no GL debug logging features.
2016-08-09 01:29:58 -04:00
fprintf(stderr, "Using AMD_debug_output extension\n");
Debug GPU functionality from soc-viewport_fx by Jason Wilkins patch number D706 with changes: - WITH_GPU_DEBUG just creates a debug context (and enables the debug messaging system functions) but leaves the checks we had intact. Old patch added the debug functionality only if we had the flag on to save some performance. Rationale here is that we might not want to recompile blender just to get the extra information, and having users start blender with a -d flag to get the extra information is also useful for bug reports. Those checks already existed and most expensive ones are hidden behind a debug mode check so performance should not be that bad. - Did some cleanup of existing functionality: When things go wrong blender side, just print the error, don't check for GL errors first. - Did not port changes needed for GLES to regular glew.h - Got rid of duplicate or very similar new functionality. Generally, code is more moving things around/cleanup and should work exactly as before apart from the debug context, so it's safe to add even now. It also provides a nice substitute function for glu error descriptions
2015-02-16 21:19:12 +01:00
glDebugMessageCallbackAMD(gpu_debug_proc_amd, mxGetCurrentContext());
glDebugMessageEnableAMD(GL_DONT_CARE, GL_DONT_CARE, 0, NULL, GL_TRUE);
OpenGL: enhance debug output When running blender --debug-gpu Display which debug facilities are available. One of these, in order of preference: - OpenGL 4.3 - KHR_debug - ARB_debug_output - AMD_debug_output All messages are logged now, not just errors. Will probably turn some of these off later. GL_DEBUG_OUTPUT_SYNCHRONOUS lets us break on errors and backtrace to the exact trouble spot. Callers of GPU_string_marker no longer pass in a message length, just the message itself (null terminated). Apple provides no GL debug logging features.
2016-08-09 01:29:58 -04:00
GPU_string_marker(success);
Debug GPU functionality from soc-viewport_fx by Jason Wilkins patch number D706 with changes: - WITH_GPU_DEBUG just creates a debug context (and enables the debug messaging system functions) but leaves the checks we had intact. Old patch added the debug functionality only if we had the flag on to save some performance. Rationale here is that we might not want to recompile blender just to get the extra information, and having users start blender with a -d flag to get the extra information is also useful for bug reports. Those checks already existed and most expensive ones are hidden behind a debug mode check so performance should not be that bad. - Did some cleanup of existing functionality: When things go wrong blender side, just print the error, don't check for GL errors first. - Did not port changes needed for GLES to regular glew.h - Got rid of duplicate or very similar new functionality. Generally, code is more moving things around/cleanup and should work exactly as before apart from the debug context, so it's safe to add even now. It also provides a nice substitute function for glu error descriptions
2015-02-16 21:19:12 +01:00
}
#endif
OpenGL: simplify debug, use only newer features Drop SciTech support & workarounds for WinCE and OpenGL ES. AMD_debug_output is still in the code but disabled. Once I verify the newer extensions are available on all the GPU + OS combos we support we can delete this disabled code.
2016-11-12 17:18:13 -06:00
else {
fprintf(stderr, "Failed to hook OpenGL debug callback.\n");
}
Debug GPU functionality from soc-viewport_fx by Jason Wilkins patch number D706 with changes: - WITH_GPU_DEBUG just creates a debug context (and enables the debug messaging system functions) but leaves the checks we had intact. Old patch added the debug functionality only if we had the flag on to save some performance. Rationale here is that we might not want to recompile blender just to get the extra information, and having users start blender with a -d flag to get the extra information is also useful for bug reports. Those checks already existed and most expensive ones are hidden behind a debug mode check so performance should not be that bad. - Did some cleanup of existing functionality: When things go wrong blender side, just print the error, don't check for GL errors first. - Did not port changes needed for GLES to regular glew.h - Got rid of duplicate or very similar new functionality. Generally, code is more moving things around/cleanup and should work exactly as before apart from the debug context, so it's safe to add even now. It also provides a nice substitute function for glu error descriptions
2015-02-16 21:19:12 +01:00
}
void gpu_debug_exit(void)
{
OpenGL: simplify debug, use only newer features Drop SciTech support & workarounds for WinCE and OpenGL ES. AMD_debug_output is still in the code but disabled. Once I verify the newer extensions are available on all the GPU + OS combos we support we can delete this disabled code.
2016-11-12 17:18:13 -06:00
if (GLEW_VERSION_4_3 || GLEW_KHR_debug) {
Make code compile with GPU_DEBUG
2015-06-26 16:18:06 +02:00
glDebugMessageCallback(NULL, NULL);
Debug GPU functionality from soc-viewport_fx by Jason Wilkins patch number D706 with changes: - WITH_GPU_DEBUG just creates a debug context (and enables the debug messaging system functions) but leaves the checks we had intact. Old patch added the debug functionality only if we had the flag on to save some performance. Rationale here is that we might not want to recompile blender just to get the extra information, and having users start blender with a -d flag to get the extra information is also useful for bug reports. Those checks already existed and most expensive ones are hidden behind a debug mode check so performance should not be that bad. - Did some cleanup of existing functionality: When things go wrong blender side, just print the error, don't check for GL errors first. - Did not port changes needed for GLES to regular glew.h - Got rid of duplicate or very similar new functionality. Generally, code is more moving things around/cleanup and should work exactly as before apart from the debug context, so it's safe to add even now. It also provides a nice substitute function for glu error descriptions
2015-02-16 21:19:12 +01:00
}
OpenGL: simplify debug, use only newer features Drop SciTech support & workarounds for WinCE and OpenGL ES. AMD_debug_output is still in the code but disabled. Once I verify the newer extensions are available on all the GPU + OS combos we support we can delete this disabled code.
2016-11-12 17:18:13 -06:00
else if (GLEW_ARB_debug_output) {
Debug GPU functionality from soc-viewport_fx by Jason Wilkins patch number D706 with changes: - WITH_GPU_DEBUG just creates a debug context (and enables the debug messaging system functions) but leaves the checks we had intact. Old patch added the debug functionality only if we had the flag on to save some performance. Rationale here is that we might not want to recompile blender just to get the extra information, and having users start blender with a -d flag to get the extra information is also useful for bug reports. Those checks already existed and most expensive ones are hidden behind a debug mode check so performance should not be that bad. - Did some cleanup of existing functionality: When things go wrong blender side, just print the error, don't check for GL errors first. - Did not port changes needed for GLES to regular glew.h - Got rid of duplicate or very similar new functionality. Generally, code is more moving things around/cleanup and should work exactly as before apart from the debug context, so it's safe to add even now. It also provides a nice substitute function for glu error descriptions
2015-02-16 21:19:12 +01:00
glDebugMessageCallbackARB(NULL, NULL);
}
OpenGL: simplify debug, use only newer features Drop SciTech support & workarounds for WinCE and OpenGL ES. AMD_debug_output is still in the code but disabled. Once I verify the newer extensions are available on all the GPU + OS combos we support we can delete this disabled code.
2016-11-12 17:18:13 -06:00
#if LEGACY_DEBUG
else if (GLEW_AMD_debug_output) {
Debug GPU functionality from soc-viewport_fx by Jason Wilkins patch number D706 with changes: - WITH_GPU_DEBUG just creates a debug context (and enables the debug messaging system functions) but leaves the checks we had intact. Old patch added the debug functionality only if we had the flag on to save some performance. Rationale here is that we might not want to recompile blender just to get the extra information, and having users start blender with a -d flag to get the extra information is also useful for bug reports. Those checks already existed and most expensive ones are hidden behind a debug mode check so performance should not be that bad. - Did some cleanup of existing functionality: When things go wrong blender side, just print the error, don't check for GL errors first. - Did not port changes needed for GLES to regular glew.h - Got rid of duplicate or very similar new functionality. Generally, code is more moving things around/cleanup and should work exactly as before apart from the debug context, so it's safe to add even now. It also provides a nice substitute function for glu error descriptions
2015-02-16 21:19:12 +01:00
glDebugMessageCallbackAMD(NULL, NULL);
}
#endif
}
OpenGL: enhance debug output When running blender --debug-gpu Display which debug facilities are available. One of these, in order of preference: - OpenGL 4.3 - KHR_debug - ARB_debug_output - AMD_debug_output All messages are logged now, not just errors. Will probably turn some of these off later. GL_DEBUG_OUTPUT_SYNCHRONOUS lets us break on errors and backtrace to the exact trouble spot. Callers of GPU_string_marker no longer pass in a message length, just the message itself (null terminated). Apple provides no GL debug logging features.
2016-08-09 01:29:58 -04:00
void GPU_string_marker(const char *buf)
Debug GPU functionality from soc-viewport_fx by Jason Wilkins patch number D706 with changes: - WITH_GPU_DEBUG just creates a debug context (and enables the debug messaging system functions) but leaves the checks we had intact. Old patch added the debug functionality only if we had the flag on to save some performance. Rationale here is that we might not want to recompile blender just to get the extra information, and having users start blender with a -d flag to get the extra information is also useful for bug reports. Those checks already existed and most expensive ones are hidden behind a debug mode check so performance should not be that bad. - Did some cleanup of existing functionality: When things go wrong blender side, just print the error, don't check for GL errors first. - Did not port changes needed for GLES to regular glew.h - Got rid of duplicate or very similar new functionality. Generally, code is more moving things around/cleanup and should work exactly as before apart from the debug context, so it's safe to add even now. It also provides a nice substitute function for glu error descriptions
2015-02-16 21:19:12 +01:00
{
OpenGL: simplify debug, use only newer features Drop SciTech support & workarounds for WinCE and OpenGL ES. AMD_debug_output is still in the code but disabled. Once I verify the newer extensions are available on all the GPU + OS combos we support we can delete this disabled code.
2016-11-12 17:18:13 -06:00
if (GLEW_VERSION_4_3 || GLEW_KHR_debug) {
Cleanup: style, gpu module
2016-01-10 07:12:10 +11:00
glDebugMessageInsert(
GL_DEBUG_SOURCE_APPLICATION, GL_DEBUG_TYPE_MARKER, 0,
OpenGL: enhance debug output When running blender --debug-gpu Display which debug facilities are available. One of these, in order of preference: - OpenGL 4.3 - KHR_debug - ARB_debug_output - AMD_debug_output All messages are logged now, not just errors. Will probably turn some of these off later. GL_DEBUG_OUTPUT_SYNCHRONOUS lets us break on errors and backtrace to the exact trouble spot. Callers of GPU_string_marker no longer pass in a message length, just the message itself (null terminated). Apple provides no GL debug logging features.
2016-08-09 01:29:58 -04:00
GL_DEBUG_SEVERITY_NOTIFICATION, -1, buf);
Debug GPU functionality from soc-viewport_fx by Jason Wilkins patch number D706 with changes: - WITH_GPU_DEBUG just creates a debug context (and enables the debug messaging system functions) but leaves the checks we had intact. Old patch added the debug functionality only if we had the flag on to save some performance. Rationale here is that we might not want to recompile blender just to get the extra information, and having users start blender with a -d flag to get the extra information is also useful for bug reports. Those checks already existed and most expensive ones are hidden behind a debug mode check so performance should not be that bad. - Did some cleanup of existing functionality: When things go wrong blender side, just print the error, don't check for GL errors first. - Did not port changes needed for GLES to regular glew.h - Got rid of duplicate or very similar new functionality. Generally, code is more moving things around/cleanup and should work exactly as before apart from the debug context, so it's safe to add even now. It also provides a nice substitute function for glu error descriptions
2015-02-16 21:19:12 +01:00
}
OpenGL: simplify debug, use only newer features Drop SciTech support & workarounds for WinCE and OpenGL ES. AMD_debug_output is still in the code but disabled. Once I verify the newer extensions are available on all the GPU + OS combos we support we can delete this disabled code.
2016-11-12 17:18:13 -06:00
else if (GLEW_ARB_debug_output) {
Cleanup: style, gpu module
2016-01-10 07:12:10 +11:00
glDebugMessageInsertARB(
GL_DEBUG_SOURCE_APPLICATION_ARB, GL_DEBUG_TYPE_OTHER_ARB, 0,
OpenGL: enhance debug output When running blender --debug-gpu Display which debug facilities are available. One of these, in order of preference: - OpenGL 4.3 - KHR_debug - ARB_debug_output - AMD_debug_output All messages are logged now, not just errors. Will probably turn some of these off later. GL_DEBUG_OUTPUT_SYNCHRONOUS lets us break on errors and backtrace to the exact trouble spot. Callers of GPU_string_marker no longer pass in a message length, just the message itself (null terminated). Apple provides no GL debug logging features.
2016-08-09 01:29:58 -04:00
GL_DEBUG_SEVERITY_LOW_ARB, -1, buf);
Debug GPU functionality from soc-viewport_fx by Jason Wilkins patch number D706 with changes: - WITH_GPU_DEBUG just creates a debug context (and enables the debug messaging system functions) but leaves the checks we had intact. Old patch added the debug functionality only if we had the flag on to save some performance. Rationale here is that we might not want to recompile blender just to get the extra information, and having users start blender with a -d flag to get the extra information is also useful for bug reports. Those checks already existed and most expensive ones are hidden behind a debug mode check so performance should not be that bad. - Did some cleanup of existing functionality: When things go wrong blender side, just print the error, don't check for GL errors first. - Did not port changes needed for GLES to regular glew.h - Got rid of duplicate or very similar new functionality. Generally, code is more moving things around/cleanup and should work exactly as before apart from the debug context, so it's safe to add even now. It also provides a nice substitute function for glu error descriptions
2015-02-16 21:19:12 +01:00
}
OpenGL: simplify debug, use only newer features Drop SciTech support & workarounds for WinCE and OpenGL ES. AMD_debug_output is still in the code but disabled. Once I verify the newer extensions are available on all the GPU + OS combos we support we can delete this disabled code.
2016-11-12 17:18:13 -06:00
#if LEGACY_DEBUG
else if (GLEW_AMD_debug_output) {
Cleanup: style, gpu module
2016-01-10 07:12:10 +11:00
glDebugMessageInsertAMD(
GL_DEBUG_CATEGORY_APPLICATION_AMD, GL_DEBUG_SEVERITY_LOW_AMD, 0,
OpenGL: enhance debug output When running blender --debug-gpu Display which debug facilities are available. One of these, in order of preference: - OpenGL 4.3 - KHR_debug - ARB_debug_output - AMD_debug_output All messages are logged now, not just errors. Will probably turn some of these off later. GL_DEBUG_OUTPUT_SYNCHRONOUS lets us break on errors and backtrace to the exact trouble spot. Callers of GPU_string_marker no longer pass in a message length, just the message itself (null terminated). Apple provides no GL debug logging features.
2016-08-09 01:29:58 -04:00
0, buf);
Debug GPU functionality from soc-viewport_fx by Jason Wilkins patch number D706 with changes: - WITH_GPU_DEBUG just creates a debug context (and enables the debug messaging system functions) but leaves the checks we had intact. Old patch added the debug functionality only if we had the flag on to save some performance. Rationale here is that we might not want to recompile blender just to get the extra information, and having users start blender with a -d flag to get the extra information is also useful for bug reports. Those checks already existed and most expensive ones are hidden behind a debug mode check so performance should not be that bad. - Did some cleanup of existing functionality: When things go wrong blender side, just print the error, don't check for GL errors first. - Did not port changes needed for GLES to regular glew.h - Got rid of duplicate or very similar new functionality. Generally, code is more moving things around/cleanup and should work exactly as before apart from the debug context, so it's safe to add even now. It also provides a nice substitute function for glu error descriptions
2015-02-16 21:19:12 +01:00
}
#endif
}
void GPU_print_error_debug(const char *str)
{
if (G.debug & G_DEBUG)
fprintf(stderr, "GPU: %s\n", str);
}
static void gpu_state_print_fl_ex(const char *name, GLenum type)
{
const unsigned char err_mark[4] = {0xff, 0xff, 0xff, 0xff};
float value[32];
int a;
memset(value, 0xff, sizeof(value));
glGetFloatv(type, value);
if (glGetError() == GL_NO_ERROR) {
printf("%s: ", name);
for (a = 0; a < 32; a++) {
if (memcmp(&value[a], err_mark, sizeof(value[a])) == 0) {
break;
}
printf("%.2f ", value[a]);
}
printf("\n");
}
}
#define gpu_state_print_fl(val) gpu_state_print_fl_ex(#val, val)
void GPU_state_print(void)
{
OpenGL: don't poll for errors, rely on KHR_debug Errors are caught & reported by our GL debug callback. This gives us way more useful information than sporadic calls to glGetError. I removed almost all use of glGetError, including our own GPU_ASSERT_NO_GL_ERRORS and GPU_CHECK_ERRORS_AROUND macros. Still used in rna_Image_gl_load because it passes unvalidated input to OpenGL functions. Still used in gpu_state_print_fl_ex as an exception handling hack -- will rewrite this soon. The optimism embodied by this commit will not prevent OpenGL errors. We need to analyze what would cause GL to fail at certain points and proactively intercept these failures. Or guarantee they can't happen.
2016-08-19 00:52:52 -04:00
/* clear any errors */
while (glGetError() != GL_NO_ERROR) {}
Debug GPU functionality from soc-viewport_fx by Jason Wilkins patch number D706 with changes: - WITH_GPU_DEBUG just creates a debug context (and enables the debug messaging system functions) but leaves the checks we had intact. Old patch added the debug functionality only if we had the flag on to save some performance. Rationale here is that we might not want to recompile blender just to get the extra information, and having users start blender with a -d flag to get the extra information is also useful for bug reports. Those checks already existed and most expensive ones are hidden behind a debug mode check so performance should not be that bad. - Did some cleanup of existing functionality: When things go wrong blender side, just print the error, don't check for GL errors first. - Did not port changes needed for GLES to regular glew.h - Got rid of duplicate or very similar new functionality. Generally, code is more moving things around/cleanup and should work exactly as before apart from the debug context, so it's safe to add even now. It also provides a nice substitute function for glu error descriptions
2015-02-16 21:19:12 +01:00
gpu_state_print_fl(GL_ACCUM_ALPHA_BITS);
gpu_state_print_fl(GL_ACCUM_BLUE_BITS);
gpu_state_print_fl(GL_ACCUM_CLEAR_VALUE);
gpu_state_print_fl(GL_ACCUM_GREEN_BITS);
gpu_state_print_fl(GL_ACCUM_RED_BITS);
gpu_state_print_fl(GL_ACTIVE_TEXTURE);
gpu_state_print_fl(GL_ALIASED_LINE_WIDTH_RANGE);
gpu_state_print_fl(GL_ALIASED_POINT_SIZE_RANGE);
gpu_state_print_fl(GL_ALPHA_BIAS);
gpu_state_print_fl(GL_ALPHA_BITS);
gpu_state_print_fl(GL_ALPHA_SCALE);
gpu_state_print_fl(GL_ALPHA_TEST);
gpu_state_print_fl(GL_ALPHA_TEST_FUNC);
gpu_state_print_fl(GL_ALPHA_TEST_REF);
gpu_state_print_fl(GL_ARRAY_BUFFER_BINDING);
gpu_state_print_fl(GL_ATTRIB_STACK_DEPTH);
gpu_state_print_fl(GL_AUTO_NORMAL);
gpu_state_print_fl(GL_AUX_BUFFERS);
gpu_state_print_fl(GL_BLEND);
gpu_state_print_fl(GL_BLEND_COLOR);
gpu_state_print_fl(GL_BLEND_DST_ALPHA);
gpu_state_print_fl(GL_BLEND_DST_RGB);
gpu_state_print_fl(GL_BLEND_EQUATION_ALPHA);
gpu_state_print_fl(GL_BLEND_EQUATION_RGB);
gpu_state_print_fl(GL_BLEND_SRC_ALPHA);
gpu_state_print_fl(GL_BLEND_SRC_RGB);
gpu_state_print_fl(GL_BLUE_BIAS);
gpu_state_print_fl(GL_BLUE_BITS);
gpu_state_print_fl(GL_BLUE_SCALE);
gpu_state_print_fl(GL_CLIENT_ACTIVE_TEXTURE);
gpu_state_print_fl(GL_CLIENT_ATTRIB_STACK_DEPTH);
gpu_state_print_fl(GL_CLIP_PLANE0);
gpu_state_print_fl(GL_COLOR_ARRAY);
gpu_state_print_fl(GL_COLOR_ARRAY_BUFFER_BINDING);
gpu_state_print_fl(GL_COLOR_ARRAY_SIZE);
gpu_state_print_fl(GL_COLOR_ARRAY_STRIDE);
gpu_state_print_fl(GL_COLOR_ARRAY_TYPE);
gpu_state_print_fl(GL_COLOR_CLEAR_VALUE);
gpu_state_print_fl(GL_COLOR_LOGIC_OP);
gpu_state_print_fl(GL_COLOR_MATERIAL);
gpu_state_print_fl(GL_COLOR_MATERIAL_FACE);
gpu_state_print_fl(GL_COLOR_MATERIAL_PARAMETER);
gpu_state_print_fl(GL_COLOR_MATRIX);
gpu_state_print_fl(GL_COLOR_MATRIX_STACK_DEPTH);
gpu_state_print_fl(GL_COLOR_SUM);
gpu_state_print_fl(GL_COLOR_TABLE);
gpu_state_print_fl(GL_COLOR_WRITEMASK);
gpu_state_print_fl(GL_COMPRESSED_TEXTURE_FORMATS);
gpu_state_print_fl(GL_CONVOLUTION_1D);
gpu_state_print_fl(GL_CONVOLUTION_2D);
gpu_state_print_fl(GL_CULL_FACE);
gpu_state_print_fl(GL_CULL_FACE_MODE);
gpu_state_print_fl(GL_CURRENT_COLOR);
gpu_state_print_fl(GL_CURRENT_FOG_COORD);
gpu_state_print_fl(GL_CURRENT_INDEX);
gpu_state_print_fl(GL_CURRENT_NORMAL);
gpu_state_print_fl(GL_CURRENT_PROGRAM);
gpu_state_print_fl(GL_CURRENT_RASTER_COLOR);
gpu_state_print_fl(GL_CURRENT_RASTER_DISTANCE);
gpu_state_print_fl(GL_CURRENT_RASTER_INDEX);
gpu_state_print_fl(GL_CURRENT_RASTER_POSITION);
gpu_state_print_fl(GL_CURRENT_RASTER_POSITION_VALID);
gpu_state_print_fl(GL_CURRENT_RASTER_SECONDARY_COLOR);
gpu_state_print_fl(GL_CURRENT_RASTER_TEXTURE_COORDS);
gpu_state_print_fl(GL_CURRENT_SECONDARY_COLOR);
gpu_state_print_fl(GL_CURRENT_TEXTURE_COORDS);
gpu_state_print_fl(GL_DEPTH_BIAS);
gpu_state_print_fl(GL_DEPTH_BITS);
gpu_state_print_fl(GL_DEPTH_CLEAR_VALUE);
gpu_state_print_fl(GL_DEPTH_FUNC);
gpu_state_print_fl(GL_DEPTH_RANGE);
gpu_state_print_fl(GL_DEPTH_SCALE);
gpu_state_print_fl(GL_DEPTH_TEST);
gpu_state_print_fl(GL_DEPTH_WRITEMASK);
gpu_state_print_fl(GL_DITHER);
gpu_state_print_fl(GL_DOUBLEBUFFER);
gpu_state_print_fl(GL_DRAW_BUFFER);
gpu_state_print_fl(GL_DRAW_BUFFER0);
gpu_state_print_fl(GL_EDGE_FLAG);
gpu_state_print_fl(GL_EDGE_FLAG_ARRAY);
gpu_state_print_fl(GL_EDGE_FLAG_ARRAY_BUFFER_BINDING);
gpu_state_print_fl(GL_EDGE_FLAG_ARRAY_STRIDE);
gpu_state_print_fl(GL_ELEMENT_ARRAY_BUFFER_BINDING);
gpu_state_print_fl(GL_FEEDBACK_BUFFER_SIZE);
gpu_state_print_fl(GL_FEEDBACK_BUFFER_TYPE);
gpu_state_print_fl(GL_FOG);
gpu_state_print_fl(GL_FOG_COLOR);
gpu_state_print_fl(GL_FOG_COORD_ARRAY);
gpu_state_print_fl(GL_FOG_COORD_ARRAY_BUFFER_BINDING);
gpu_state_print_fl(GL_FOG_COORD_ARRAY_STRIDE);
gpu_state_print_fl(GL_FOG_COORD_ARRAY_TYPE);
gpu_state_print_fl(GL_FOG_COORD_SRC);
gpu_state_print_fl(GL_FOG_DENSITY);
gpu_state_print_fl(GL_FOG_END);
gpu_state_print_fl(GL_FOG_HINT);
gpu_state_print_fl(GL_FOG_INDEX);
gpu_state_print_fl(GL_FOG_MODE);
gpu_state_print_fl(GL_FOG_START);
OpenGL: clean up use of old extensions
2015-11-24 02:20:38 -05:00
gpu_state_print_fl(GL_FRAGMENT_PROGRAM_ARB); /* TODO: remove ARB program support */
Debug GPU functionality from soc-viewport_fx by Jason Wilkins patch number D706 with changes: - WITH_GPU_DEBUG just creates a debug context (and enables the debug messaging system functions) but leaves the checks we had intact. Old patch added the debug functionality only if we had the flag on to save some performance. Rationale here is that we might not want to recompile blender just to get the extra information, and having users start blender with a -d flag to get the extra information is also useful for bug reports. Those checks already existed and most expensive ones are hidden behind a debug mode check so performance should not be that bad. - Did some cleanup of existing functionality: When things go wrong blender side, just print the error, don't check for GL errors first. - Did not port changes needed for GLES to regular glew.h - Got rid of duplicate or very similar new functionality. Generally, code is more moving things around/cleanup and should work exactly as before apart from the debug context, so it's safe to add even now. It also provides a nice substitute function for glu error descriptions
2015-02-16 21:19:12 +01:00
gpu_state_print_fl(GL_FRAGMENT_SHADER_DERIVATIVE_HINT);
gpu_state_print_fl(GL_FRONT_FACE);
gpu_state_print_fl(GL_GENERATE_MIPMAP_HINT);
gpu_state_print_fl(GL_GREEN_BIAS);
gpu_state_print_fl(GL_GREEN_BITS);
gpu_state_print_fl(GL_GREEN_SCALE);
gpu_state_print_fl(GL_HISTOGRAM);
gpu_state_print_fl(GL_INDEX_ARRAY);
gpu_state_print_fl(GL_INDEX_ARRAY_BUFFER_BINDING);
gpu_state_print_fl(GL_INDEX_ARRAY_STRIDE);
gpu_state_print_fl(GL_INDEX_ARRAY_TYPE);
gpu_state_print_fl(GL_INDEX_BITS);
gpu_state_print_fl(GL_INDEX_CLEAR_VALUE);
gpu_state_print_fl(GL_INDEX_LOGIC_OP);
gpu_state_print_fl(GL_INDEX_MODE);
gpu_state_print_fl(GL_INDEX_OFFSET);
gpu_state_print_fl(GL_INDEX_SHIFT);
gpu_state_print_fl(GL_INDEX_WRITEMASK);
gpu_state_print_fl(GL_LIGHT0);
gpu_state_print_fl(GL_LIGHT1);
gpu_state_print_fl(GL_LIGHT2);
gpu_state_print_fl(GL_LIGHT3);
gpu_state_print_fl(GL_LIGHT4);
gpu_state_print_fl(GL_LIGHT5);
gpu_state_print_fl(GL_LIGHT6);
gpu_state_print_fl(GL_LIGHT7);
gpu_state_print_fl(GL_LIGHTING);
gpu_state_print_fl(GL_LIGHT_MODEL_AMBIENT);
gpu_state_print_fl(GL_LIGHT_MODEL_COLOR_CONTROL);
gpu_state_print_fl(GL_LIGHT_MODEL_LOCAL_VIEWER);
gpu_state_print_fl(GL_LIGHT_MODEL_TWO_SIDE);
gpu_state_print_fl(GL_LINE_SMOOTH);
gpu_state_print_fl(GL_LINE_SMOOTH_HINT);
gpu_state_print_fl(GL_LINE_STIPPLE);
gpu_state_print_fl(GL_LINE_STIPPLE_PATTERN);
gpu_state_print_fl(GL_LINE_STIPPLE_REPEAT);
gpu_state_print_fl(GL_LINE_WIDTH);
gpu_state_print_fl(GL_LINE_WIDTH_GRANULARITY);
gpu_state_print_fl(GL_LINE_WIDTH_RANGE);
gpu_state_print_fl(GL_LIST_BASE);
gpu_state_print_fl(GL_LIST_INDEX);
gpu_state_print_fl(GL_LIST_MODE);
gpu_state_print_fl(GL_LOGIC_OP);
gpu_state_print_fl(GL_LOGIC_OP_MODE);
gpu_state_print_fl(GL_MAP1_COLOR_4);
gpu_state_print_fl(GL_MAP1_GRID_DOMAIN);
gpu_state_print_fl(GL_MAP1_GRID_SEGMENTS);
gpu_state_print_fl(GL_MAP1_INDEX);
gpu_state_print_fl(GL_MAP1_NORMAL);
gpu_state_print_fl(GL_MAP1_TEXTURE_COORD_1);
gpu_state_print_fl(GL_MAP1_TEXTURE_COORD_2);
gpu_state_print_fl(GL_MAP1_TEXTURE_COORD_3);
gpu_state_print_fl(GL_MAP1_TEXTURE_COORD_4);
gpu_state_print_fl(GL_MAP1_VERTEX_3);
gpu_state_print_fl(GL_MAP1_VERTEX_4);
gpu_state_print_fl(GL_MAP2_COLOR_4);
gpu_state_print_fl(GL_MAP2_GRID_DOMAIN);
gpu_state_print_fl(GL_MAP2_GRID_SEGMENTS);
gpu_state_print_fl(GL_MAP2_INDEX);
gpu_state_print_fl(GL_MAP2_NORMAL);
gpu_state_print_fl(GL_MAP2_TEXTURE_COORD_1);
gpu_state_print_fl(GL_MAP2_TEXTURE_COORD_2);
gpu_state_print_fl(GL_MAP2_TEXTURE_COORD_3);
gpu_state_print_fl(GL_MAP2_TEXTURE_COORD_4);
gpu_state_print_fl(GL_MAP2_VERTEX_3);
gpu_state_print_fl(GL_MAP2_VERTEX_4);
gpu_state_print_fl(GL_MAP_COLOR);
gpu_state_print_fl(GL_MAP_STENCIL);
gpu_state_print_fl(GL_MATRIX_MODE);
gpu_state_print_fl(GL_MAX_3D_TEXTURE_SIZE);
gpu_state_print_fl(GL_MAX_ATTRIB_STACK_DEPTH);
gpu_state_print_fl(GL_MAX_CLIENT_ATTRIB_STACK_DEPTH);
gpu_state_print_fl(GL_MAX_CLIP_PLANES);
gpu_state_print_fl(GL_MAX_COLOR_MATRIX_STACK_DEPTH);
gpu_state_print_fl(GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS);
gpu_state_print_fl(GL_MAX_CUBE_MAP_TEXTURE_SIZE);
gpu_state_print_fl(GL_MAX_DRAW_BUFFERS);
gpu_state_print_fl(GL_MAX_ELEMENTS_INDICES);
gpu_state_print_fl(GL_MAX_ELEMENTS_VERTICES);
gpu_state_print_fl(GL_MAX_EVAL_ORDER);
gpu_state_print_fl(GL_MAX_FRAGMENT_UNIFORM_COMPONENTS);
gpu_state_print_fl(GL_MAX_LIGHTS);
gpu_state_print_fl(GL_MAX_LIST_NESTING);
gpu_state_print_fl(GL_MAX_MODELVIEW_STACK_DEPTH);
gpu_state_print_fl(GL_MAX_NAME_STACK_DEPTH);
gpu_state_print_fl(GL_MAX_PIXEL_MAP_TABLE);
gpu_state_print_fl(GL_MAX_PROJECTION_STACK_DEPTH);
gpu_state_print_fl(GL_MAX_TEXTURE_COORDS);
gpu_state_print_fl(GL_MAX_TEXTURE_IMAGE_UNITS);
gpu_state_print_fl(GL_MAX_TEXTURE_LOD_BIAS);
gpu_state_print_fl(GL_MAX_TEXTURE_SIZE);
gpu_state_print_fl(GL_MAX_TEXTURE_STACK_DEPTH);
gpu_state_print_fl(GL_MAX_TEXTURE_UNITS);
gpu_state_print_fl(GL_MAX_VARYING_FLOATS);
gpu_state_print_fl(GL_MAX_VERTEX_ATTRIBS);
gpu_state_print_fl(GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS);
gpu_state_print_fl(GL_MAX_VERTEX_UNIFORM_COMPONENTS);
gpu_state_print_fl(GL_MAX_VIEWPORT_DIMS);
gpu_state_print_fl(GL_MINMAX);
gpu_state_print_fl(GL_MODELVIEW_MATRIX);
gpu_state_print_fl(GL_MODELVIEW_STACK_DEPTH);
gpu_state_print_fl(GL_MULTISAMPLE);
gpu_state_print_fl(GL_NAME_STACK_DEPTH);
gpu_state_print_fl(GL_NORMALIZE);
gpu_state_print_fl(GL_NORMAL_ARRAY);
gpu_state_print_fl(GL_NORMAL_ARRAY_BUFFER_BINDING);
gpu_state_print_fl(GL_NORMAL_ARRAY_STRIDE);
gpu_state_print_fl(GL_NORMAL_ARRAY_TYPE);
gpu_state_print_fl(GL_NUM_COMPRESSED_TEXTURE_FORMATS);
gpu_state_print_fl(GL_PACK_ALIGNMENT);
gpu_state_print_fl(GL_PACK_IMAGE_HEIGHT);
gpu_state_print_fl(GL_PACK_LSB_FIRST);
gpu_state_print_fl(GL_PACK_ROW_LENGTH);
gpu_state_print_fl(GL_PACK_SKIP_IMAGES);
gpu_state_print_fl(GL_PACK_SKIP_PIXELS);
gpu_state_print_fl(GL_PACK_SKIP_ROWS);
gpu_state_print_fl(GL_PACK_SWAP_BYTES);
gpu_state_print_fl(GL_PERSPECTIVE_CORRECTION_HINT);
gpu_state_print_fl(GL_PIXEL_MAP_A_TO_A_SIZE);
gpu_state_print_fl(GL_PIXEL_MAP_B_TO_B_SIZE);
gpu_state_print_fl(GL_PIXEL_MAP_G_TO_G_SIZE);
gpu_state_print_fl(GL_PIXEL_MAP_I_TO_A_SIZE);
gpu_state_print_fl(GL_PIXEL_MAP_I_TO_B_SIZE);
gpu_state_print_fl(GL_PIXEL_MAP_I_TO_G_SIZE);
gpu_state_print_fl(GL_PIXEL_MAP_I_TO_I_SIZE);
gpu_state_print_fl(GL_PIXEL_MAP_I_TO_R_SIZE);
gpu_state_print_fl(GL_PIXEL_MAP_R_TO_R_SIZE);
gpu_state_print_fl(GL_PIXEL_MAP_S_TO_S_SIZE);
gpu_state_print_fl(GL_PIXEL_PACK_BUFFER_BINDING);
gpu_state_print_fl(GL_PIXEL_UNPACK_BUFFER_BINDING);
gpu_state_print_fl(GL_POINT_DISTANCE_ATTENUATION);
gpu_state_print_fl(GL_POINT_FADE_THRESHOLD_SIZE);
gpu_state_print_fl(GL_POINT_SIZE);
gpu_state_print_fl(GL_POINT_SIZE_GRANULARITY);
gpu_state_print_fl(GL_POINT_SIZE_MAX);
gpu_state_print_fl(GL_POINT_SIZE_MIN);
gpu_state_print_fl(GL_POINT_SIZE_RANGE);
gpu_state_print_fl(GL_POINT_SMOOTH);
gpu_state_print_fl(GL_POINT_SMOOTH_HINT);
gpu_state_print_fl(GL_POINT_SPRITE);
gpu_state_print_fl(GL_POLYGON_MODE);
gpu_state_print_fl(GL_POLYGON_OFFSET_FACTOR);
gpu_state_print_fl(GL_POLYGON_OFFSET_FILL);
gpu_state_print_fl(GL_POLYGON_OFFSET_LINE);
gpu_state_print_fl(GL_POLYGON_OFFSET_POINT);
gpu_state_print_fl(GL_POLYGON_OFFSET_UNITS);
gpu_state_print_fl(GL_POLYGON_SMOOTH);
gpu_state_print_fl(GL_POLYGON_SMOOTH_HINT);
gpu_state_print_fl(GL_POLYGON_STIPPLE);
gpu_state_print_fl(GL_POST_COLOR_MATRIX_ALPHA_BIAS);
gpu_state_print_fl(GL_POST_COLOR_MATRIX_ALPHA_SCALE);
gpu_state_print_fl(GL_POST_COLOR_MATRIX_BLUE_BIAS);
gpu_state_print_fl(GL_POST_COLOR_MATRIX_BLUE_SCALE);
gpu_state_print_fl(GL_POST_COLOR_MATRIX_COLOR_TABLE);
gpu_state_print_fl(GL_POST_COLOR_MATRIX_GREEN_BIAS);
gpu_state_print_fl(GL_POST_COLOR_MATRIX_GREEN_SCALE);
gpu_state_print_fl(GL_POST_COLOR_MATRIX_RED_BIAS);
gpu_state_print_fl(GL_POST_COLOR_MATRIX_RED_SCALE);
gpu_state_print_fl(GL_POST_CONVOLUTION_ALPHA_BIAS);
gpu_state_print_fl(GL_POST_CONVOLUTION_ALPHA_SCALE);
gpu_state_print_fl(GL_POST_CONVOLUTION_BLUE_BIAS);
gpu_state_print_fl(GL_POST_CONVOLUTION_BLUE_SCALE);
gpu_state_print_fl(GL_POST_CONVOLUTION_COLOR_TABLE);
gpu_state_print_fl(GL_POST_CONVOLUTION_GREEN_BIAS);
gpu_state_print_fl(GL_POST_CONVOLUTION_GREEN_SCALE);
gpu_state_print_fl(GL_POST_CONVOLUTION_RED_BIAS);
gpu_state_print_fl(GL_POST_CONVOLUTION_RED_SCALE);
gpu_state_print_fl(GL_PROJECTION_MATRIX);
gpu_state_print_fl(GL_PROJECTION_STACK_DEPTH);
gpu_state_print_fl(GL_READ_BUFFER);
gpu_state_print_fl(GL_RED_BIAS);
gpu_state_print_fl(GL_RED_BITS);
gpu_state_print_fl(GL_RED_SCALE);
gpu_state_print_fl(GL_RENDER_MODE);
gpu_state_print_fl(GL_RESCALE_NORMAL);
gpu_state_print_fl(GL_RGBA_MODE);
gpu_state_print_fl(GL_SAMPLES);
gpu_state_print_fl(GL_SAMPLE_BUFFERS);
gpu_state_print_fl(GL_SAMPLE_COVERAGE_INVERT);
gpu_state_print_fl(GL_SAMPLE_COVERAGE_VALUE);
gpu_state_print_fl(GL_SCISSOR_BOX);
gpu_state_print_fl(GL_SCISSOR_TEST);
gpu_state_print_fl(GL_SECONDARY_COLOR_ARRAY);
gpu_state_print_fl(GL_SECONDARY_COLOR_ARRAY_BUFFER_BINDING);
gpu_state_print_fl(GL_SECONDARY_COLOR_ARRAY_SIZE);
gpu_state_print_fl(GL_SECONDARY_COLOR_ARRAY_STRIDE);
gpu_state_print_fl(GL_SECONDARY_COLOR_ARRAY_TYPE);
gpu_state_print_fl(GL_SELECTION_BUFFER_SIZE);
gpu_state_print_fl(GL_SEPARABLE_2D);
gpu_state_print_fl(GL_SHADE_MODEL);
gpu_state_print_fl(GL_SMOOTH_LINE_WIDTH_GRANULARITY);
gpu_state_print_fl(GL_SMOOTH_LINE_WIDTH_RANGE);
gpu_state_print_fl(GL_SMOOTH_POINT_SIZE_GRANULARITY);
gpu_state_print_fl(GL_SMOOTH_POINT_SIZE_RANGE);
gpu_state_print_fl(GL_STENCIL_BACK_FAIL);
gpu_state_print_fl(GL_STENCIL_BACK_FUNC);
gpu_state_print_fl(GL_STENCIL_BACK_PASS_DEPTH_FAIL);
gpu_state_print_fl(GL_STENCIL_BACK_PASS_DEPTH_PASS);
gpu_state_print_fl(GL_STENCIL_BACK_REF);
gpu_state_print_fl(GL_STENCIL_BACK_VALUE_MASK);
gpu_state_print_fl(GL_STENCIL_BACK_WRITEMASK);
gpu_state_print_fl(GL_STENCIL_BITS);
gpu_state_print_fl(GL_STENCIL_CLEAR_VALUE);
gpu_state_print_fl(GL_STENCIL_FAIL);
gpu_state_print_fl(GL_STENCIL_FUNC);
gpu_state_print_fl(GL_STENCIL_PASS_DEPTH_FAIL);
gpu_state_print_fl(GL_STENCIL_PASS_DEPTH_PASS);
gpu_state_print_fl(GL_STENCIL_REF);
gpu_state_print_fl(GL_STENCIL_TEST);
gpu_state_print_fl(GL_STENCIL_VALUE_MASK);
gpu_state_print_fl(GL_STENCIL_WRITEMASK);
gpu_state_print_fl(GL_STEREO);
gpu_state_print_fl(GL_SUBPIXEL_BITS);
gpu_state_print_fl(GL_TEXTURE_1D);
gpu_state_print_fl(GL_TEXTURE_2D);
gpu_state_print_fl(GL_TEXTURE_3D);
gpu_state_print_fl(GL_TEXTURE_BINDING_1D);
gpu_state_print_fl(GL_TEXTURE_BINDING_2D);
gpu_state_print_fl(GL_TEXTURE_BINDING_3D);
gpu_state_print_fl(GL_TEXTURE_BINDING_CUBE_MAP);
gpu_state_print_fl(GL_TEXTURE_COMPRESSION_HINT);
gpu_state_print_fl(GL_TEXTURE_COORD_ARRAY);
gpu_state_print_fl(GL_TEXTURE_COORD_ARRAY_BUFFER_BINDING);
gpu_state_print_fl(GL_TEXTURE_COORD_ARRAY_SIZE);
gpu_state_print_fl(GL_TEXTURE_COORD_ARRAY_STRIDE);
gpu_state_print_fl(GL_TEXTURE_COORD_ARRAY_TYPE);
gpu_state_print_fl(GL_TEXTURE_CUBE_MAP);
gpu_state_print_fl(GL_TEXTURE_GEN_Q);
gpu_state_print_fl(GL_TEXTURE_GEN_R);
gpu_state_print_fl(GL_TEXTURE_GEN_S);
gpu_state_print_fl(GL_TEXTURE_GEN_T);
gpu_state_print_fl(GL_TEXTURE_MATRIX);
gpu_state_print_fl(GL_TEXTURE_STACK_DEPTH);
gpu_state_print_fl(GL_TRANSPOSE_COLOR_MATRIX);
gpu_state_print_fl(GL_TRANSPOSE_MODELVIEW_MATRIX);
gpu_state_print_fl(GL_TRANSPOSE_PROJECTION_MATRIX);
gpu_state_print_fl(GL_TRANSPOSE_TEXTURE_MATRIX);
gpu_state_print_fl(GL_UNPACK_ALIGNMENT);
gpu_state_print_fl(GL_UNPACK_IMAGE_HEIGHT);
gpu_state_print_fl(GL_UNPACK_LSB_FIRST);
gpu_state_print_fl(GL_UNPACK_ROW_LENGTH);
gpu_state_print_fl(GL_UNPACK_SKIP_IMAGES);
gpu_state_print_fl(GL_UNPACK_SKIP_PIXELS);
gpu_state_print_fl(GL_UNPACK_SKIP_ROWS);
gpu_state_print_fl(GL_UNPACK_SWAP_BYTES);
gpu_state_print_fl(GL_VERTEX_ARRAY);
gpu_state_print_fl(GL_VERTEX_ARRAY_BUFFER_BINDING);
gpu_state_print_fl(GL_VERTEX_ARRAY_SIZE);
gpu_state_print_fl(GL_VERTEX_ARRAY_STRIDE);
gpu_state_print_fl(GL_VERTEX_ARRAY_TYPE);
gpu_state_print_fl(GL_VERTEX_PROGRAM_POINT_SIZE);
gpu_state_print_fl(GL_VERTEX_PROGRAM_TWO_SIDE);
gpu_state_print_fl(GL_VIEWPORT);
gpu_state_print_fl(GL_ZOOM_X);
gpu_state_print_fl(GL_ZOOM_Y);
}
#undef gpu_state_print_fl
Copy Permalink