Summary: | [softpipe] piglit fp-long-alu regression | ||
---|---|---|---|
Product: | Mesa | Reporter: | Vinson Lee <vlee> |
Component: | Mesa core | Assignee: | mesa-dev |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | eric, kenneth |
Version: | git | Keywords: | bisected, have-backtrace, regression |
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Vinson Lee
2014-08-11 21:19:54 UTC
The Mesa IR optimizer creates a lot of immediates when it evaluates constant expressions, but doesn't eliminate them. You can easily get hundreds of unused immediates, which is what is happening with fp-long-alu. That sounds pretty easy to fix, but we could also just disable the Mesa IR optimizer for ARB_fragment_programs. Notably, in my commit, I measured gains for ARB_vp, but only losses from enabling it in ARB_fp... *** Bug 82471 has been marked as a duplicate of this bug. *** commit 55a57834bf912916a5e07486b32f1778b35657f6 Author: Carl Worth <cworth@cworth.org> Date: Thu Feb 12 10:14:24 2015 -0800 Revert use of Mesa IR optimizer for ARB_fragment_programs Commit f82f2fb3dc770902f1657ab1c22e6004faa3afab added use of the Mesa IR optimizer for both ARB_fragment_program and ARB_vertex_program, but only justified the vertex-program portions with measured performance improvements. Meanwhile, the optimizer was seen to generate hundreds of unused immediates without discarding them, causing failures. Discard the use of the optimizer for now to fix the regression. (In the future, we anticpate things moving from Mesa IR to NIR for better optimization anyway.) Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=82477 Reviewed-by: Ian Romanick <ian.d.romanick@intel.com> CC: "10.3 10.4 10.5" <mesa-stable@lists.freedesktop.org> |
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.