1. 05 Apr, 2019 1 commit
  2. 04 Apr, 2019 3 commits
  3. 03 Apr, 2019 2 commits
  4. 02 Apr, 2019 1 commit
    • build: Don't ship GTEST headers in install target · 1d1fd885
      Karl Schultz authored
      A project that uses googletest(GTEST) shouldn't include googletest
      headers with its artifacts in its install target.  These headers
      simply are not needed by the consumers of the install target and
      can cause conflicts with other projects that use googletest
      themselves and this project's install target.  And they are just not
      part of the expected glslang build artifacts.
      
      It is likely that the addition of the googletest headers to the install
      target was a simple oversight that happens as a result of adding
      googletest as a CMake subdirectory.
      
      For more information on how this causes conflicts with other projects,
      please see: https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues/821.
  5. 28 Mar, 2019 1 commit
  6. 27 Mar, 2019 3 commits
  7. 26 Mar, 2019 2 commits
  8. 19 Mar, 2019 2 commits
  9. 18 Mar, 2019 5 commits
  10. 17 Mar, 2019 1 commit
  11. 12 Mar, 2019 3 commits
  12. 11 Mar, 2019 1 commit
  13. 07 Mar, 2019 2 commits
  14. 06 Mar, 2019 4 commits
    • Move getBufferReferenceAlignment to be a method of TType · 7895e473
      Jeff Bolz authored
      This is a better place for it logically, since it is not specific to
      glsl->spirv translation. And in a future change I want to use it outside
      of glslangtospv.
    • Improved fix for buffer reference constants · 3fd12326
      Jeff Bolz authored
      This is an alternate fix for the issue described in commit be63facd, whose
      solution didn't work if there were non-trivial operations involved in computing
      a constant initializer which caused the 'constant unfolding' code to kick in
      (addConstantReferenceConversion). Instead, this change does the 'unfolding'
      later in createSpvConstantFromConstUnionArray. If a reference-type constant has
      survived that long, then folding is already done, this must be a 'real' (inside
      a function) use of the constant, and it should be safe to unfold and apply the
      bitcast.
    • Merge pull request #1714 from jeffbolznv/volatil · 79d25ea0
      John Kessenich authored
      Fix interactions between 'volatile' and the Vulkan memory model
    • Build: Update to latest SPIR-V header. · cc4a756d
      John Kessenich authored
  15. 05 Mar, 2019 1 commit
    • Fix interactions between 'volatile' and the Vulkan memory model · 38cbad15
      Jeff Bolz authored
      Last year we changed 'volatile' to also act as 'coherent', but when I
      resolved the memory model changes against that change I missed handling
      volatile in a couple places that we check for coherent. There was also
      a place in post-processing that acted as if the volatile memory access
      flag has a literal number associated with it, when it doesn't.
  16. 04 Mar, 2019 3 commits
  17. 28 Feb, 2019 2 commits
  18. 26 Feb, 2019 2 commits
  19. 25 Feb, 2019 1 commit