[Bug 105224] Webgl Pointclouds flickers
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sun Feb 25 20:58:31 UTC 2018
https://bugs.freedesktop.org/show_bug.cgi?id=105224
Mark Janes <mark.a.janes at intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|medium |highest
Severity|normal |blocker
Blocks| |104757
Assignee|intel-3d-bugs at lists.freedes |itoral at igalia.com
|ktop.org |
CC| |kenneth at whitecape.org,
| |mark.a.janes at intel.com
Keywords| |bisected, regression
Status|NEW |ASSIGNED
--- Comment #14 from Mark Janes <mark.a.janes at intel.com> ---
Bisected to:
commit 16631ca30ea6d6eec8101f07d97a55b2210026e8
Author: Iago Toral Quiroga <itoral at igalia.com>
Date: Fri Oct 13 09:22:54 2017 +0200
i965/sbe: fix active components for SSO programs with over 16 inputs
When we have up to 16 FS inputs, the SF unit will reorder our inputs
to be consecutive, however, when we have more than 16 we need to
to read our inputs from the URB exactly as they have been
output from the previous stage. This means that for SSO we have to
consider if we have URB padding due to unused input locations.
Specifically, this affects gen9 active components programming, since
for things to work in scenarios with over 16 inputs that have padded
regions we need to ensure that we program active components for the
padded regions too. If we don't do this the hardware won't read
the URB properly for inputs located after padded regions.
Found empirically.
Fixes (these also require a patch in CTS):
KHR-GL45.enhanced_layouts.varying_locations
KHR-GL45.enhanced_layouts.varying_array_locations
Reviewed-by: Kenneth Graunke <kenneth at whitecape.org>
Referenced Bugs:
https://bugs.freedesktop.org/show_bug.cgi?id=104757
[Bug 104757] [TRACKER] Mesa 18.0 release tracker
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20180225/f6fb1123/attachment.html>
More information about the intel-3d-bugs
mailing list