1. 21 Dec, 2017 5 commits
  2. 20 Dec, 2017 6 commits
  3. 19 Dec, 2017 4 commits
  4. 18 Dec, 2017 3 commits
  5. 15 Dec, 2017 6 commits
    • Revert "Vulkan: Roll loader/validation layers SDK. (2/2)" · 647dca76
      Jamie Madill authored
      This reverts commit f15f9cec.
      
      Reason for revert:
      Causing a compile failure on the Fuchsia config, due to a path
      difference. Will fix upstream and re-land, since it's breaking the
      auto-roller.
      
      https://chromium-review.googlesource.com/c/chromium/src/+/829878
      
      FAILED: clang_x64/gen/third_party/angle/src/vulkan_support/angle/vulkan/parameter_validation.cpp 
      python ../../third_party/vulkan-validation-layers/src/scripts/lvl_genvk.py -o clang_x64/gen/third_party/angle/src/vulkan_support/angle/vulkan -registry ../../third_party/vulkan-validation-layers/src/scripts/vk.xml parameter_validation.cpp -quiet
      Error: Could not find vk_validation_error_messages.h
      [906/1359] ACTION //third_party/angle/src/vulkan_support:vulkan_gen_object_tracker_cpp(//build/toolchain/linux:clang_x64)
      FAILED: clang_x64/gen/third_party/angle/src/vulkan_support/angle/vulkan/object_tracker.cpp 
      python ../../third_party/vulkan-validation-layers/src/scripts/lvl_genvk.py -o clang_x64/gen/third_party/angle/src/vulkan_support/angle/vulkan -registry ../../third_party/vulkan-validation-layers/src/scripts/vk.xml object_tracker.cpp -quiet
      Error: Could not find vk_validation_error_messages.h
      
      Original change's description:
      > Vulkan: Roll loader/validation layers SDK. (2/2)
      > 
      > This hasn't been updated in a while, so there are many changes.
      > It should also include better validation for memory barriers.
      > 
      > Also includes updated builds for SPIRV Tools and glslang.
      > A few pull requests need to land before landing this in ANGLE.
      > 
      > This second step re-enables Vulkan and includes the updated build.
      > 
      > Includes a workaround for parameter_validation.h no longer being
      > auto-generated, and the stale file clobbering the build.
      > 
      > Also includes a fix for an incorrect memory barrier.
      > 
      > Bug: angleproject:2237
      > Change-Id: Iae611764870281ed6aa7b187ec0c4e44226c722a
      > Reviewed-on: https://chromium-review.googlesource.com/759197
      > Commit-Queue: Jamie Madill <jmadill@chromium.org>
      > Reviewed-by: Frank Henigman <fjhenigman@chromium.org>
      
      TBR=fjhenigman@chromium.org,jmadill@chromium.org,cwallez@chromium.org
      
      # Not skipping CQ checks because original CL landed > 1 day ago.
      
      Bug: angleproject:2237
      Change-Id: I9bc60860668c1da773b6e2fdb83ecc20215e9125
      Reviewed-on: https://chromium-review.googlesource.com/830926Reviewed-by: 's avatarJamie Madill <jmadill@chromium.org>
      Commit-Queue: Jamie Madill <jmadill@chromium.org>
    • Support ozone/gbm back end in standalone gn build. · 1955640a
      Frank Henigman authored
      This makes it possible to do a standalone gn build of the ozone/gbm back
      end by using the following gn args.
        use_ozone = true
        ozone_platform_gbm = true
      
      BUG=angleproject:1569
      
      Change-Id: I70716b83943dae95df48b847ff8cca5e2c555c4a
      Reviewed-on: https://chromium-review.googlesource.com/749867
      Commit-Queue: Frank Henigman <fjhenigman@chromium.org>
      Reviewed-by: 's avatarYuly Novikov <ynovikov@chromium.org>
    • Add angle_link_glx arg to standalone gn build. · e42ec189
      Frank Henigman authored
      Port the angle_link_glx setting of the gyp build to the standalone gn build.
      When set to true, libGL will be linked into libANGLE, instead of dlopen-ed.
      This is useful when using apitrace.
      
      BUG=angleproject:1569
      
      Change-Id: I16a91504960169efdcde3b2c50b944de148d9ba6
      Reviewed-on: https://chromium-review.googlesource.com/821691Reviewed-by: 's avatarCorentin Wallez <cwallez@chromium.org>
      Commit-Queue: Frank Henigman <fjhenigman@chromium.org>
    • Fix Bug in Intel Workaround · 9fc87331
      Brandon Jones authored
      Fixes an incorrect assert that is hit when trying to find a program
      output when none are present. It is valid to not have an output, so we
      should not check for an output when there are none.
      
      Bug:angleproject:2283
      Change-Id: Ia640482870c6ee589a933b989272177760237e3b
      Reviewed-on: https://chromium-review.googlesource.com/825957
      Commit-Queue: Jamie Madill <jmadill@chromium.org>
      Reviewed-by: 's avatarJamie Madill <jmadill@chromium.org>
    • ES31: Implement image state query · 9c8e1a36
      Xinghua Cao authored
      BUG=angleproject:2278
      TEST=dEQP-GLES31.functional.state_query.indexed.image_binding*
      
      Change-Id: Ia624d55ccf1fdf92188d9e710265bdffe96a23c6
      Reviewed-on: https://chromium-review.googlesource.com/810465
      Commit-Queue: Corentin Wallez <cwallez@chromium.org>
      Reviewed-by: 's avatarCorentin Wallez <cwallez@chromium.org>
    • Always create TVariables for TIntermSymbol nodes · 195be942
      Olli Etuaho authored
      TIntermSymbol nodes are now constructed based on a specific TVariable.
      This makes sure that all TIntermSymbol nodes that are created to refer
      to a specific temporary in an AST transform will have consistent data.
      The TVariable objects are not necessarily added to the symbol table
      levels - just those variables that can be referred to by their name
      during parsing need to be reachable through there.
      
      In the future this can be taken a step further so that TIntermSymbol
      nodes just to point to a TVariable instead of duplicating the
      information.
      
      BUG=angleproject:2267
      TEST=angle_unittests
      
      Change-Id: I4e7bcdb0637cd3b588d3c202ef02f4b7bd7954a1
      Reviewed-on: https://chromium-review.googlesource.com/811925
      Commit-Queue: Olli Etuaho <oetuaho@nvidia.com>
      Reviewed-by: 's avatarCorentin Wallez <cwallez@chromium.org>
  6. 14 Dec, 2017 4 commits
    • D3D11: Fix program uniform buffer dity bits. · f414121d
      Jamie Madill authored
      There were actually three missing state synchronization points:
      
      1. When re-binding a uniform buffer, we had no dirty bits.
      2. When modifying the Program bindings, we also had no update.
      3. When triggering a dependent state update via BufferData.
      
      This fixes all the missing syncs and adds tests for the cases.
      
      Bug: angleproject:1390
      Change-Id: I2f05766545784248bcca8308ae34ac5720237ab1
      Reviewed-on: https://chromium-review.googlesource.com/823150
      Commit-Queue: Jamie Madill <jmadill@chromium.org>
      Reviewed-by: 's avatarYuly Novikov <ynovikov@chromium.org>
      Reviewed-by: 's avatarKai Ninomiya <kainino@chromium.org>
      Reviewed-by: 's avatarJamie Madill <jmadill@chromium.org>
    • ES31: Remove support of GL_OES_geometry_shader in compiler · bd924af1
      Jiawei Shao authored
      This patch intends to remove the support of GL_OES_geometry_shader
      in ANGLE compiler.
      
      To make the implementation simpler, currently we decide to only
      support "GL_EXT_geometry_shader" as the extension string of geometry
      shader in ANGLE.
      
      This patch also updates all the related shaders in angle_unittests
      into R"()" format.
      
      BUG=angleproject:1941
      TEST=angle_unittests
      
      Change-Id: Ife9858abeedfb46b02c5c2fb1cda16fa27198511
      Reviewed-on: https://chromium-review.googlesource.com/773451
      Commit-Queue: Corentin Wallez <cwallez@chromium.org>
      Reviewed-by: 's avatarCorentin Wallez <cwallez@chromium.org>
    • Vulkan: Roll loader/validation layers SDK. (2/2) · f15f9cec
      Jamie Madill authored
      This hasn't been updated in a while, so there are many changes.
      It should also include better validation for memory barriers.
      
      Also includes updated builds for SPIRV Tools and glslang.
      A few pull requests need to land before landing this in ANGLE.
      
      This second step re-enables Vulkan and includes the updated build.
      
      Includes a workaround for parameter_validation.h no longer being
      auto-generated, and the stale file clobbering the build.
      
      Also includes a fix for an incorrect memory barrier.
      
      Bug: angleproject:2237
      Change-Id: Iae611764870281ed6aa7b187ec0c4e44226c722a
      Reviewed-on: https://chromium-review.googlesource.com/759197
      Commit-Queue: Jamie Madill <jmadill@chromium.org>
      Reviewed-by: 's avatarFrank Henigman <fjhenigman@chromium.org>
    • Classify TSymbols using an enum · 9d4d7f06
      Olli Etuaho authored
      Symbols can be either built-ins, user-defined, nameless, or for
      ANGLE's internal use. In addition we currently use TFunction symbols
      that are not yet resolved - they might later resolve to either a
      built-in or a user-defined function. Record this information in each
      TSymbol so that TSymbol contains sufficient information for deciding
      how to format symbol names in output.
      
      The goal is to eventually replace current uses of TName with pointers
      to different TSymbol objects. So far only built-ins and user-defined
      symbols have associated TSymbol objects, but that will be expanded to
      cover ANGLE's internal symbols as well.
      
      BUG=angleproject:2267
      TEST=angle_unittests
      
      Change-Id: I927ce023fe257cc236da82c127700f3bd72bfe96
      Reviewed-on: https://chromium-review.googlesource.com/816952
      Commit-Queue: Olli Etuaho <oetuaho@nvidia.com>
      Reviewed-by: 's avatarCorentin Wallez <cwallez@chromium.org>
  7. 13 Dec, 2017 11 commits
  8. 12 Dec, 2017 1 commit
    • Add test for Chromium's EGL_D3D_TEXTURE pbuffer creation · 3acfc625
      Corentin Wallez authored
      When creating the pbuffer, Chromium specifies EGL_WIDTH and EGL_HEIGHT
      attributes that are unnecessary because they are extracted from the
      D3D11 texture passed as <buffer> to eglCreatePbufferFromClientBuffer.
      
      This is a regression test for crbug.com/794086 where a change to
      ValidateCreatePbufferFromClientBuffer made EGL_WIDTH and EGL_HEIGHT
      invalid for <buftype> EGL_D3D_TEXTURE and caused Chromium to fail
      creating the pbuffer, causing all black rendering.
      
      BUG=chromium:794086
      
      Change-Id: I262fd0991e0f46f255aeac25528ddb4a62fa1309
      Reviewed-on: https://chromium-review.googlesource.com/822296Reviewed-by: 's avatarJamie Madill <jmadill@chromium.org>
      Commit-Queue: Corentin Wallez <cwallez@chromium.org>