1. 16 Oct, 2019 8 commits
  2. 14 Oct, 2019 3 commits
  3. 11 Oct, 2019 1 commit
    • Stencil buffer texture sampling · 1c462ebc
      Alexis Hetu authored
      In order to perform a blitFramebuffer operation, ANGLE uses
      a compute shader which reads the stencil from a depth+stencil
      image to a buffer, and then copies this buffer to the stencil
      of the other image.
      
      This cl basically treats VK_FORMAT_S8_UINT as VK_FORMAT_R8_UINT
      with quad layout for the purpose of texture sampling.
      
      Fixes the following tests:
      dEQP-GLES3.functional.fbo.blit.depth_stencil.depth32f_stencil8_basic
      dEQP-GLES3.functional.fbo.blit.depth_stencil.depth32f_stencil8_stencil_only
      dEQP-GLES3.functional.fbo.blit.depth_stencil.depth24_stencil8_basic
      dEQP-GLES3.functional.fbo.blit.depth_stencil.depth24_stencil8_stencil_only
      
      Bug: b/142385547
      Change-Id: Ib2ea7fa81496ceca1c24ea7f065b1c2cd05596ee
      Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/37188
      Presubmit-Ready: Alexis Hétu <sugoi@google.com>
      Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
      Tested-by: 's avatarAlexis Hétu <sugoi@google.com>
      Reviewed-by: 's avatarAntonio Maiorano <amaiorano@google.com>
  4. 07 Oct, 2019 2 commits
  5. 05 Oct, 2019 2 commits
  6. 04 Oct, 2019 8 commits
  7. 03 Oct, 2019 2 commits
  8. 02 Oct, 2019 8 commits
  9. 01 Oct, 2019 5 commits
  10. 30 Sep, 2019 1 commit
    • Optimize "max(t, t)" to fold into just "t" · a9dc7707
      Sean Risser authored
      This masks a crash related to nested, unconditional continue statements.
      Those constructs are known to be buggy, but we have elected to not fix
      them at this point in time because the SWANGLE project will deprecate
      all of Swiftshader's GLES backend.
      
      It's unlikely that the remaining bug will effect many end-users as it
      relies on bizarre control flow.
      
      For logging purposes here is the shader code that reproduces an infinite
      loop:
      
          void foo() { }
      
          void main() {
      	for (int i = 0; i < 4; i++) {
      	    continue;
      	    for (int k = 0; k < 4; k++)
      		continue;
      	    foo();
      	}
          }
      
      I'm not adding this as a unit test since we aren't fixing our compiler.
      
      Bug chromium:997283
      
      Change-Id: Id31d70c4cd70a16fd20b7ebed18a82d5f8a705ba
      Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36708Tested-by: 's avatarSean Risser <srisser@google.com>
      Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
      Reviewed-by: 's avatarAlexis Hétu <sugoi@google.com>
      Reviewed-by: 's avatarNicolas Capens <nicolascapens@google.com>