Summary: | [ILK] HL2 & CS:Source water shader broken | ||
---|---|---|---|
Product: | Mesa | Reporter: | Chris Forbes <chrisf> |
Component: | Drivers/DRI/i965 | Assignee: | Chris Forbes <chrisf> |
Status: | RESOLVED FIXED | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Severity: | normal | ||
Priority: | medium | CC: | idr, jason, rhyskidd |
Version: | 10.4 | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Bug Depends on: | |||
Bug Blocks: | 77449 | ||
Attachments: | INTEL_DEBUG=fs,ann output on ILK |
Description
Chris Forbes
2014-12-17 00:15:06 UTC
Any ideas what's wrong in the SIMD16 version of the shader? Are we not enforcing some other ILK SIMD16 restriction? INTEL_DEBUG=fs output would be very helpful. Created attachment 114129 [details]
INTEL_DEBUG=fs,ann output on ILK
Chris and I noticed that the sampler message type appears to be totally bogus - it says "sample_l" instead of "sample" sometimes. This turned out to be a bug in the disassembler. Chris said he'd put together patches to fix that. So that's a red herring - don't get lost there. Appears to be fixed on master as of 14/2/2016. (And something has made a big difference to performance, too!) Confirmed here as well on ILK. Visual corruption no longer visible on the water shaders, and certain other effects that had negative performance hits (i.e. fire) don't appear to do so now. No hard data however to back that up, but Chris' report aligns with my experience. $ glxinfo | grep OpenGL OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Ironlake Mobile OpenGL version string: 2.1 Mesa 11.2.0-devel (git-816c987 2016-02-14 wily-oibaf-ppa) OpenGL shading language version string: 1.20 Do we have any idea how recent the fix is? It would be interesting to get a bisect to know what fixed it. But I also don't expect either of you to bisect it across thousands of commits. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.