Summary: | src/gallium/auxiliary/gallivm/lp_bld_format_aos.c:707:lp_build_fetch_rgba_aos: Assertion `0' failed. | ||
---|---|---|---|
Product: | Mesa | Reporter: | Vinson Lee <vlee> |
Component: | Other | Assignee: | Jose Fonseca <jfonseca> |
Status: | CLOSED FIXED | QA Contact: | |
Severity: | critical | ||
Priority: | medium | CC: | airlied, brianp, jfonseca |
Version: | git | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Vinson Lee
2011-10-25 11:04:42 UTC
a441feb757b1be4845ba378f0207dcdc5cc1a407 is the first bad commit commit a441feb757b1be4845ba378f0207dcdc5cc1a407 Author: Dave Airlie <airlied@redhat.com> Date: Mon Sep 19 15:04:48 2011 +0100 gallium: add initial pure integer support (v2) This add support for unsigned/signed integer types via adding a 'pure' bit in the format description table. It adds 4 new u_format get/put hooks, for get/put uint and get/put sint so that accessors can get native access to the integer bits. This is used to avoid precision loss via float converting paths. It doesn't add any float fetchers for these types at the moment, GL doesn't require float fetching from these types and I expect we'll introduce a lot of hidden bugs if we start allowing such conversions without an API mandating it. It adds all formats from EXT_texture_integer and EXT_texture_rg. 0 regressions on llvmpipe here with this. (there is some more follow on code in my gallium-int-work branch, bringing softpipe and mesa to a pretty integer clean state) v2: fixup python generator to get signed->unsigned and unsigned->signed fetches working. Signed-off-by: Dave Airlie <airlied@redhat.com> :040000 040000 19b1c549f2a58f65d107d1d7c3d0b661be3b77c0 ec5d6945a107616343556abda9186d9b0a4aeb4f M src bisect run success should be fixed now in master with commit d404f6069307699206c134924cdd124d04ae2266 mesa: 69e48e7220f018d874e85eea6962ec58b1feba87 (master) Verified fixed. |
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.