[Mesa-dev] About tests for extensions that are later integrated in the core specs

[Andres Gomez]

Hi,

as complementary work to the one done to "Add FP64 support to the i965
shader backends" at:
https://bugs.freedesktop.org/show_bug.cgi?id=92760

We've been working to add piglit tests that would check the new features
added by this addition. Because of this, we have created several
generators.

Checking other generators that also apply to fp64, we have seen that
those generate "duplicated" tests for:
      * glsl-4.00
      * arb_gpu_shader_fp64

Probably, this makes sense but we are also seeing that individual tests
that are coded for the extension at:
      * tests/spec/arb_gpu_shader_fp64

Do not have a counterpart at:
      * tests/spec/glsl-4.00

So, the question would be, when doing tests for an extension:
      * Should we make the generators create "duplicated" tests for the
        extension and for the glsl version that takes the features of
        the extension into the core? Our guess is, "yes".
      * Should we duplicate also the individual tests in the same way?
        Our guess is, again, "yes", but we do not know if this would be
        too overkill.

-- 
Br,

Andres
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20160304/b2e5b334/attachment.sig>