[Mesa-dev] [Bug 106283] Shader replacements works only for limited use cases
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Apr 27 13:29:21 UTC 2018
https://bugs.freedesktop.org/show_bug.cgi?id=106283
Bug ID: 106283
Summary: Shader replacements works only for limited use cases
Product: Mesa
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: medium
Component: glsl-compiler
Assignee: mesa-dev at lists.freedesktop.org
Reporter: iive at yahoo.com
QA Contact: intel-3d-bugs at lists.freedesktop.org
In the mesa documentation here: https://www.mesa3d.org/shading.html#envvars
you can find a section about "Shader Replacement" that tells you how you can
dump the source of GLSL shaders and even replace some shaders with your own.
Unfortunately, I couldn't make this work for the app that is having a problem.
I dig a bit in the Mesa code and came to the conclusion that the dump&replace
works only for the glProgramStringARB(), while the app seems to provide the
shader through glShaderSourceARB() that seems to be completely separate from
the code that supports dump&replace.
It would be nice if this feature could work with all code paths.
In the past, I've been able to narrow down at least two R600 assembly bugs, by
tweaking the shaders that generate them (using d3d9 library that can do that).
It's very disappointing that Mesa has the functionality, but it works only for
a limited code paths.
At very least, document properly that quirk.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20180427/ef15503b/attachment.html>
More information about the mesa-dev
mailing list