On Thu, Dec 6, 2018 at 7:36 PM Mark Janes <mark.a.ja...@intel.com> wrote: > > This series provides Intel shader compilation debug information via > KHR_debug. Previously, shader assembly and related compilation > artifacts were dumped to stderr. Tools associating compilation > artifacts with programs (e.g. FrameRetrace*) parsed stderr, which was > error prone. Changes to the shader debug formats and the addition of > shader cache assembly dumps further complicate the task of parsing > stderr. > > KHR_debug provides synchronous callbacks with stable identifiers, > simplifying the task of matching debug artifacts with the originating > GLSL.
One observation is that while the identifiers may be stable within a single execution, they will not be stable across different applications / traces. id's are set on a first-come first-serve basis, so depending on the exact order, the id's will end up different. Is that OK for frameretrace? Another approach would be to create globally-hardcoded id's for these, and start the auto-allocation in a higher range. -ilia _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
