[Bug 96298] 32-bit failures for spec.arb_compute_shader.execution.atomic-counter
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue May 31 22:13:59 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=96298
Jordan Justen <jljusten at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |currojerez at riseup.net
--- Comment #1 from Jordan Justen <jljusten at gmail.com> ---
tests/spec/arb_compute_shader/execution/atomic-counter.shader_test
uses atomic_uint, which should be a 32-bit value on 64-bit processes
as well. The test has a uint atomic counter that starts at 0, and gets
decremented 512 times.
Does this test have a similar failure?
tests/spec/arb_shader_atomic_counters/execution/atomic-counter.shader_test
https://www.opengl.org/registry/specs/ARB/shader_atomic_counters.txt
says "Increments and decrements at the limit of the range will wrap
to [0, 2^32-1]", so I think the test is valid. The shader_runner
code looks valid for treating the buffer as a uint32_t pointer.
--
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20160531/dbdc9dc5/attachment.html>
More information about the intel-3d-bugs
mailing list