[Bug 109216] 4-27% performance drop in Vulkan benchmarks

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Jan 9 20:56:19 UTC 2019


--- Comment #9 from Ian Romanick <idr at freedesktop.org> ---
(In reply to Eero Tamminen from comment #5)
> (In reply to Lionel Landwerlin from comment #4)
> > commit 8fb8ebfbb05d3323481c8ba6d320b3a3580bad99
> > Author: Ian Romanick <ian.d.romanick at intel.com>
> > Date:   Tue May 22 18:56:41 2018 -0700
> > 
> >     intel/compiler: More peephole select
> >     
> >     Shader-db results:
> >     
> >     The one shader hurt for instructions is a compute shader that had both
> >     spills and fills hurt.
> I think shaders in Sacha Willems' Vulkan demos would also need to be added
> to shader-db.  According to INTEL_DEBUG output, Deferred Multisampling demo
> doesn't have any compute shaders or spills/fills, and it regressed most.

Adding the GLSL shader won't actually help this problem.  We'd have to add the
SPIR-V instead.  The issue is the weird way that glslang generates for-loops. 
I have a test case that reproduces the issue in plain GLSL.

You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20190109/7fb68b13/attachment.html>

More information about the intel-3d-bugs mailing list