1. 06 Mar, 2019 3 commits
  2. 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.
  3. 04 Mar, 2019 2 commits
    • Merge pull request #1699 from jeffbolznv/buffer_reference_fold · 9390154c
      John Kessenich authored
      Handle buffer references vs 'const'
    • Handle buffer references vs 'const' · be63facd
      Jeff Bolz authored
      Allow constructors to and from references to be constant folded. Section 4.3.3
      says constructors whose arguments are all constant expressions must fold.
      
      Disallow 'const' on buffer reference types. It is not a 'non-void transparent
      basic data type' (it is not considered 'basic').
      
      Handle buffer reference constants (which can be assigned to a non-const reference,
      or can be further folded to another type of constant) by converting to
      'constructor(uint64_t constant)' in addConversion.
      
      Disallow == and != operators on reference types.
  4. 28 Feb, 2019 2 commits
  5. 26 Feb, 2019 2 commits
  6. 22 Feb, 2019 2 commits
  7. 21 Feb, 2019 7 commits
  8. 20 Feb, 2019 3 commits
    • Fixup leak of TString · 0560138e
      Dan Sinclair authored
      In decomposeIntrinsic a new TString was being allocated and passed into
      a TVariable. That string was leaking. This CL converts the new TString
      to call NewPoolTString to allocate from the TString pool.
    • Allocate empty function name in the string pool. · 756bfd0a
      Dan Sinclair authored
      Inside the grammar for function_identifier if the .function is null an
      empty function name is allocated. This is allocated on the stack and
      passed into TFunction as a pointer. TFunction just stores that pointer.
      
      Later, when we access the name we will receive an invalid usage of a
      stack allocated variable. This CL switches to using NewPoolTStringn for
      the empty function name.
    • Update SPIRV-Tools known good · f8939eff
      Greg Fischer authored
  9. 19 Feb, 2019 4 commits
  10. 17 Feb, 2019 1 commit
  11. 16 Feb, 2019 1 commit
  12. 14 Feb, 2019 2 commits
  13. 12 Feb, 2019 1 commit
  14. 11 Feb, 2019 6 commits
  15. 09 Feb, 2019 1 commit
  16. 08 Feb, 2019 2 commits