1. 17 Sep, 2011 1 commit
  2. 16 Sep, 2011 2 commits
  3. 15 Sep, 2011 1 commit
  4. 12 Sep, 2011 1 commit
  5. 11 Sep, 2011 1 commit
  6. 09 Sep, 2011 10 commits
  7. 08 Sep, 2011 9 commits
  8. 07 Sep, 2011 10 commits
    • Paul Berry's avatar
      Test implicit sizing of gl_TexCoord. · f9d6bf7e
      Paul Berry authored
      From the GLSL 1.10 spec section 7.6 (Varying Variables):
      
        As with all arrays, indices used to subscript gl_TexCoord must
        either be an integral constant expressions, or this array must be
        re-declared by the shader with a size. The size can be at most
        gl_MaxTextureCoords.
      
      This patch adds test to verify that when gl_TexCoord is implicitly
      sized, it is an error to access it with an integral constant
      expression equal to gl_MaxTextureCoords.
      
      I've verified that these tests pass on the nVidia proprietary Linux
      driver.
      Reviewed-by: default avatarIan Romanick <ian.d.romanick@intel.com>
      f9d6bf7e
    • Paul Berry's avatar
      Fragment shader tests for clipDistance sizing. · e4405c7a
      Paul Berry authored
      This patch adds two new tests,
      fs-clip-distance-explicitly-sized.shader_test and
      fs-clip-distance-sizeable-to-max.shader_test, to verify that the
      clipDistance array behaves properly when its size is explicitly set in
      the fragment shader.
      
      These tests parallel the existing tests,
      vs-clip-distance-explicitly-sized.shader_test and
      vs-clip-distance-sizeable-to-max.shader_test, which were testing the
      equivalent functionality in the vertex shader.
      Reviewed-by: default avatarIan Romanick <ian.d.romanick@intel.com>
      e4405c7a
    • Paul Berry's avatar
      Clip distance: Test error conditions for implicitly sized gl_ClipDistance. · fc63b3f1
      Paul Berry authored
      These tests verify that it is illegal to use the .length() method on
      gl_ClipDistance when it is implicitly sized, or to access it using an
      index that is not a constant.
      Reviewed-by: default avatarIan Romanick <ian.d.romanick@intel.com>
      fc63b3f1
    • Paul Berry's avatar
      Add trivial clip tests. · ca90aba8
      Paul Berry authored
      These tests verify correct behavior when gl_ClipDistance and
      gl_ClipVertex are set to constant values.
      Reviewed-by: default avatarIan Romanick <ian.d.romanick@intel.com>
      ca90aba8
    • Paul Berry's avatar
      gl_ClipDistance: Add better max size checks. · ccd88a6c
      Paul Berry authored
      These new tests validate that an appropriate error is generated when:
      - attempting to access beyond the end of gl_ClipDistance when explicitly sized
        to 3.
      - attempting to access beyond the end of gl_ClipDistance when explicitly sized
        to gl_MaxClipDistances.
      - attempting to explicitly size gl_ClipDistance beyond gl_MaxClipDistances.
      - same as above, but without accessing gl_ClipDistance.
      - attempting to access beyond the end of gl_ClipDistance when implicitly sized.
      
      These tests replace clip-distance-not-sizeable-above-max.c, which was less thorough, and more unweildy since it was a straight C program.
      Reviewed-by: default avatarIan Romanick <ian.d.romanick@intel.com>
      ccd88a6c
    • Paul Berry's avatar
      Add --check-link option to glslparsertest. · af8051dc
      Paul Berry authored
      This option tells glslparsertest to treat link errors the same as
      compile errors.  For tests that expect a result of "pass", this causes
      glslparsertest to verify that the shader both compiles and links
      without error.  For tests that expect a result of "fail", this causes
      glslparsertest to treat a link-time error as passing the test, just as
      it would a compile-time error.
      Reviewed-by: default avatarIan Romanick <ian.d.romanick@intel.com>
      af8051dc
    • Paul Berry's avatar
      Remove bogus vs-clip-distance-implicitly-sized.shader_test. · fbb5a36f
      Paul Berry authored
      This test was attempting to verify that the GLSL compiler properly
      computed the size of the gl_ClipDistance array when it was implicitly
      sized, by calling .length() on the array.  But according to the GLSL
      spec, it is illegal to call .length() on an implicitly sized array.
      
      Because of this, it is actually impossible to tell using a test
      whether the GLSL compiler properly computed the size of an
      implicitly-sized array; all we can do is attempt to use all elements
      of the array and make sure nothing breaks.  The test
      vs-clip-distance-all-planes-enabled.shader_test already does this.  So
      I've removed the bogus test.
      Reviewed-by: default avatarIan Romanick <ian.d.romanick@intel.com>
      fbb5a36f
    • Paul Berry's avatar
      Fix fs-clip-distance-interpolated.shader_test (implicit array size rules). · 6df79f43
      Paul Berry authored
      This test accesses gl_ClipDistance using a non-constant array index.
      GLSL requires that such accesses only be made to explicitly sized
      arrays.  So add an explicit declaration of the size of
      gl_ClipDistance.
      Reviewed-by: default avatarIan Romanick <ian.d.romanick@intel.com>
      6df79f43
    • Paul Berry's avatar
      Fix generated "op-mod" tests to actually test the modulus operator. · 5dd2f867
      Paul Berry authored
      Due to a copy-paste bug on my part, the generated "op-mod" tests
      actually weren't testing the "%" operator at all.  They were testing
      the "/" operator (and were thus identical to the "op-div" tests).
      This patch fixes the tests to actually test the "%" operator.
      5dd2f867
    • Christoph Bumiller's avatar
      generated tests: add large uints division test for GLSL 1.3 · 70b2af55
      Christoph Bumiller authored
      At least some of these divisions should fail on implementations
      that naively use 32 bit float division (without refinement).
      Reviewed-by: Paul Berry's avatarPaul Berry <stereotype441@gmail.com>
      70b2af55
  9. 05 Sep, 2011 5 commits