Summary: | [regression bisected] R600 fp64 and glsl-4.00 piglit failures | ||
---|---|---|---|
Product: | Mesa | Reporter: | James Harvey <lothmordor> |
Component: | Drivers/Gallium/r600 | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED FIXED | QA Contact: | Default DRI bug account <dri-devel> |
Severity: | normal | ||
Priority: | medium | CC: | jv356 |
Version: | git | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
piglit comparison summary
Emit double precision FMA |
Description
James Harvey
2016-07-02 10:50:26 UTC
Created attachment 124867 [details] [review] Emit double precision FMA Does the attached patch help? Hi Jan, Yes, the patch fixed all of the regressed piglits. It looks like these are now fixed as well: spec/arb_gpu_shader_fp64/execution/conversion/frag-conversion-explicit-dvec3-bvec3: fail pass spec/arb_gpu_shader_fp64/execution/conversion/frag-conversion-explicit-dvec4-bvec4: fail pass spec/arb_gpu_shader_fp64/execution/conversion/geom-conversion-explicit-dvec3-bvec3: fail pass spec/arb_gpu_shader_fp64/execution/conversion/geom-conversion-explicit-dvec4-bvec4: fail pass spec/arb_gpu_shader_fp64/execution/conversion/vert-conversion-explicit-dvec3-bvec3: fail pass spec/arb_gpu_shader_fp64/execution/conversion/vert-conversion-explicit-dvec4-bvec4: fail pass spec/glsl-4.00/execution/conversion/frag-conversion-explicit-dvec3-bvec3: fail pass spec/glsl-4.00/execution/conversion/frag-conversion-explicit-dvec4-bvec4: fail pass spec/glsl-4.00/execution/conversion/geom-conversion-explicit-dvec3-bvec3: fail pass spec/glsl-4.00/execution/conversion/geom-conversion-explicit-dvec4-bvec4: fail pass spec/glsl-4.00/execution/conversion/vert-conversion-explicit-dvec3-bvec3: fail pass spec/glsl-4.00/execution/conversion/vert-conversion-explicit-dvec4-bvec4: fail pass Thanks! Tested-by: James Harvey <lothmordor@gmail.com> I've pushed the fix. Closing. |
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.