[Mesa-dev] [Bug 94957] dEQP failures on llvmpipe

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat Apr 16 00:47:10 UTC 2016


--- Comment #4 from Roland Scheidegger <sroland at vmware.com> ---
(In reply to Ilia Mirkin from comment #3)
> I will start a fresh run with these parameters. A random blending test makes
> it seem like it completely fails. I'd like to encourage you to grab a copy
> of deqp and run it yourself to see the details - you get expected and actual
> images among other things.
> <TestCaseResult Version="0.3.3"
> CasePath="dEQP-GLES3.functional.fragment_ops.blend.default_framebuffer.
> rgb_func_alpha_func.src.dst_color_one_minus_src_alpha"
> CaseType="SelfValidate">
>  <Text>RGB equation = GL_FUNC_ADD</Text>
>  <Text>RGB src func = GL_DST_COLOR</Text>
>  <Text>RGB dst func = GL_ONE</Text>
>  <Text>Alpha equation = GL_FUNC_ADD</Text>
>  <Text>Alpha src func = GL_ONE_MINUS_SRC_ALPHA</Text>
>  <Text>Alpha dst func = GL_ONE</Text>
>  <Text>Blend color = (0.2, 0.4, 0.6, 0.8)</Text>
>  <Text>Image comparison failed: max difference = (97, 97, 97, 1), threshold
> = (4, 4, 4, 4)</Text>

Yes, that looks quite wrong indeed - and not precision related of course.
I'll give it a try...

> (paste that into the url bar of your browser) makes it seem like something
> funny is going on. Green = good, red = bad. This is running on a SKL with
> LLVM 3.7.1 in case it matters.
Ideally it should of course not, albeit different bugs with and without AVX are
possible, as quite different code paths may be used due to 8x32 vs. 4x32
vectors (if you use LP_NATIVE_VECTOR_WIDTH=128 it will disable avx). Of course
it's also possible llvm miscompiles things in which case the llvm version would
matter, but that should be rare.

You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20160416/9937befc/attachment-0001.html>

More information about the mesa-dev mailing list