On Wed, Apr 24, 2019 at 12:59 AM Mark Janes wrote:
> I pushed the patches that got review (1-3). I haven't prompted anyone
> for more review, because FrameRetrace is the only app that will
> immediately benefit from the patches. Eventually, the existing
> mechanism will break, and someone that
I pushed the patches that got review (1-3). I haven't prompted anyone
for more review, because FrameRetrace is the only app that will
immediately benefit from the patches. Eventually, the existing
mechanism will break, and someone that needs to debug their shader
assemblies will have a reason to
Did this get dropped on the ground?
On Fri, Dec 7, 2018 at 12:07 PM Mark Janes wrote:
> Ilia Mirkin writes:
>
> > On Thu, Dec 6, 2018 at 7:36 PM Mark Janes
> wrote:
> >>
> >> This series provides Intel shader compilation debug information via
> >> KHR_debug. Previously, shader assembly and
Ilia Mirkin writes:
> On Thu, Dec 6, 2018 at 7:36 PM Mark Janes 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
Patches 1-3:
Reviewed-by: Erik Faye-Lund
On Thu, 2018-12-06 at 16:35 -0800, Mark Janes 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
On Thu, Dec 6, 2018 at 7:36 PM Mark Janes 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.
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
