Summary: | [PNV] Regression in Piglit test general/two-sided-lighting-separate-specular | ||
---|---|---|---|
Product: | Mesa | Reporter: | Paul Berry <stereotype441> |
Component: | Drivers/DRI/i915 | Assignee: | Paul Berry <stereotype441> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | 8.0 | ||
Hardware: | All | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Bug Depends on: | |||
Bug Blocks: | 42993 |
Description
Paul Berry
2012-02-10 20:06:08 UTC
Patch sent to Mesa list for review: From: Paul Berry <stereotype441@gmail.com> Date: Fri, 10 Feb 2012 19:51:55 -0800 Subject: [PATCH] i915: Fix type of "specoffset" variable. Commit 2e5a1a2 (intel: Convert from GLboolean to 'bool' from stdbool.h.) converted the "specoffset" local variable (in intel_tris.c) from a GLboolean to a bool. However, GLboolean was the wrong type for specoffset--it should have been a GLuint (to match the declaration of specoffset in struct intel_context). This patch changes specoffset to the proper type. Fixes piglit test general/two-sided-lighting-separate-specular. Fixed on 8.0 branch by: commit e55f2d97f61420f6004c60be4238799f7a35b440 Author: Paul Berry <stereotype441@gmail.com> Date: Fri Feb 10 19:51:55 2012 -0800 i915: Fix type of "specoffset" variable. Commit 2e5a1a2 (intel: Convert from GLboolean to 'bool' from stdbool.h.) converted the "specoffset" local variable (in intel_tris.c) from a GLboolean to a bool. However, GLboolean was the wrong type for specoffset--it should have been a GLuint (to match the declaration of specoffset in struct intel_context). This patch changes specoffset to the proper type. Fixes piglit test general/two-sided-lighting-separate-specular. This is a candidate for stable branches. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=45917 Reviewed-by: Kenneth Graunke <kenneth@whitecape.org> (cherry picked from commit 6b0a07f9ce844a8a96e2583bd37ed8453bf151c6) |
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.