tests: Introduce an OpenGL shader runner.
2 unresolved threads
2 unresolved threads
Merge request reports
Activity
- tests/shader_runner_gl.c 0 → 100644
67 68 struct vkd3d_shader_combined_resource_sampler *combined_samplers; 69 unsigned int combined_sampler_count; 70 }; 71 72 static struct gl_runner *gl_runner(struct shader_runner *r) 73 { 74 return CONTAINING_RECORD(r, struct gl_runner, r); 75 } 76 77 static void debug_output(GLenum source, GLenum type, GLuint id, GLenum severity, 78 GLsizei length, const GLchar *message, const void *userParam) 79 { 80 if (message[length - 1] == '\n') 81 --length; 82 trace("%.*s\n", length, message); This is a bit annoyingly chatty, at least on my setup. It prints a lot of messages like:
shader_runner_gl:82: Section [test], line 40: Shader Stats: SGPRS: 32 VGPRS: 16 Code Size: 200 LDS: 0 Scratch: 0 Max Waves: 20 Spilled SGPRs: 0 Spilled VGPRs: 0 PrivMem VGPRs: 0 Outputs: 0 PatchOutputs: 0 DivergentLoop: 0 InlineUniforms: 0 (VS, W32) shader_runner_gl:82: Section [test], line 40: Shader Stats: SGPRS: 8 VGPRS: 8 Code Size: 60 LDS: 0 Scratch: 0 Max Waves: 20 Spilled SGPRs: 0 Spilled VGPRs: 0 PrivMem VGPRs: 0 Outputs: 1 PatchOutputs: 0 DivergentLoop: 0 InlineUniforms: 0 (PS, W32)
That's s bit more than what I consider sensible for a default verbosity level. Could that be reduced?
That's s bit more than what I consider sensible for a default verbosity level. Could that be reduced?
Sure, glDebugMessageControl() can be used to tweak what gets reported. I guess those are GL_DEBUG_SEVERITY_NOTIFICATION messages, but you can check what debug_output() receives for "type" and "severity" to see what to disable.
added 23 commits
-
9d2264ac...4e1bf5e1 - 22 commits from branch
wine:master
- beb3f6e0 - tests: Introduce an OpenGL shader runner.
-
9d2264ac...4e1bf5e1 - 22 commits from branch
mentioned in merge request !1168 (closed)
Please register or sign in to reply