https://bugs.freedesktop.org/show_bug.cgi?id=105095
Bug ID: 105095 Summary: piglit arb_vertex_type_2_10_10_10_rev-array_types failed for BARTS Product: Mesa Version: 17.3 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel@lists.freedesktop.org Reporter: benau2006@yahoo.com.hk QA Contact: dri-devel@lists.freedesktop.org
Output of arb_vertex_type_2_10_10_10_rev-array_types from piglit tests:
testing: RGBA SINT testing: RGBA SNORM Probe color at (25,5) Expected: 0.500000 0.250000 0.000000 1.000000 Observed: 0.501961 0.250980 0.000000 0.333333 testing: RGBA UINT testing: RGBA UNORM testing: BGRA SNORM Probe color at (85,5) Expected: 0.000000 0.250000 0.500000 1.000000 Observed: 0.000000 0.250980 0.501961 0.333333 testing: BGRA UNORM Mesa version 17.3.3 AMD/ATI Barts PRO Radeon HD 6850
Detail in https://github.com/supertuxkart/stk-code/issues/3097, this bug cause wrong animation in stk.
And i think 2.2 / 2.3 equation isn't causing this bug, because from what i see zero is represented correctly in stk, also some amd devs told me barts switched to use the new formula long time ago.
Any idea?
https://bugs.freedesktop.org/show_bug.cgi?id=105095
--- Comment #1 from Roland Scheidegger sroland@vmware.com --- Is that BARTS specific? My piglit runs with Juniper (HD 5750) show this test passing (and generally there's no difference in the driver between these two chips). (Albeit I never ran it with this specific mesa version, you could try mesa git.)
https://bugs.freedesktop.org/show_bug.cgi?id=105095
--- Comment #2 from Roland Scheidegger sroland@vmware.com --- FWIW this looks very similar to a bug recently fixed for radv. Probably not so coincidentally, radeonsi has workarounds for 2/10/10/10 signed formats, apparently gcn hw before vega (with the exception of stoney ridge) has a bug interpreting the 2bit alpha as unsigned. The output from this test would be consistent with that (alpha 1.0 as 2 bit snorm would be 0x01, whereas that value interpreted as unorm would be 0.333). So maybe the same bug could affect later evergreen hw as well.
https://bugs.freedesktop.org/show_bug.cgi?id=105095
GitLab Migration User gitlab-migration@fdo.invalid changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED
--- Comment #3 from GitLab Migration User gitlab-migration@fdo.invalid --- -- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/629.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org