when i run software that need shaders on mesa-17.2.0-rc6
i have black windows with this comments:
./qemu-system-ppc64 -m 1024 -cpu G4 -display sdl,gl=on -M mac99
qemu_gl_create_compile_shader: compile vertex error
0:4(9): error: syntax error, unexpected $end, expecting ',' or ';'
qemu_gl_create_compile_shader: compile fragment error
0:4(19): error: syntax error, unexpected $end, expecting ',' or ';'
This is with Darkplace quake:
(line offset for any above warnings/errors: 50)
GLSL shader glsl/default.glsl depth/shadow failed! some features may not work properly.
vertex shader compile log:
0:91(17): error: syntax error, unexpected $end, expecting ';'
Hope will help build
Tested on 17.2 offical and same issue
this come on Mame
../../../../../src/osd/modules/opengl/gl_shader_tool.cpp:358: GL Error: object 0x1 compilation failed
../../../../../src/osd/modules/opengl/gl_shader_tool.cpp:358 glInfoLog: 0:2(6): error: syntax error, unexpected $end, expecting ',' or ';'
failed to process shader: <
gl_TexCoord = gl_TextureMatrix * gl_MultiTexCoord0;
gl_Position = ftransform();
Shader shown seems fine. Can you bisect mesa to track the offending commit?
hi emil i can try but im not the best to this things .
if you gave me an hand step by step i can try. for sure the issue come after rc4 that was for sure the last i was build and was working ok on my system
If you have a working Apitrace trace, ezBench could be used to automatically bisect which Mesa commits cause changes in rendering i.e. regresses it.
ezBench is here:
You need to set up "user_parameters.sh" file so that ezBench can build Mesa & run it with Apitrace, and have a folder with the apitrace trace file used for render validation + a file which tells which frame in the trace is used for comparison.
README tells how to setup & use ezBench. I will add some documentation on how to do the Apitrace validation (to the example parameter file).
Hi Emil and Aero,
the issue is fixed i had been tested with last mesa git.
but new one come if i build with radeonsi, amdgpu and with an ld error.
i will open a new bug report.