1. 14 Dec, 2017 3 commits
    • 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>
  2. 13 Dec, 2017 11 commits
  3. 12 Dec, 2017 6 commits
  4. 11 Dec, 2017 1 commit
  5. 09 Dec, 2017 1 commit
  6. 07 Dec, 2017 2 commits
  7. 06 Dec, 2017 4 commits
  8. 05 Dec, 2017 6 commits
  9. 04 Dec, 2017 5 commits
  10. 02 Dec, 2017 1 commit
    • Simplify parsing struct field declarators · d5f44c98
      Olli Etuaho authored
      This removes the dummy type that was attached to struct declarators
      while parsing. This makes TParseContext::addStructDeclaratorList in
      particular simpler to understand.
      
      The new TDeclarator data type is the parsed representation of the
      struct_declarator grammar rule. It is completely immutable. The name
      and location stored in TField can also be qualified as constant now.
      
      BUG=angleproject:2267
      TEST=angle_unittests
      
      Change-Id: I2834f87fc0eee0bdb7673ef495a55fb463023c55
      Reviewed-on: https://chromium-review.googlesource.com/797033
      Commit-Queue: Olli Etuaho <oetuaho@nvidia.com>
      Reviewed-by: 's avatarJamie Madill <jmadill@chromium.org>