1. 10 Nov, 2018 1 commit
    • ParseHelper: assign global XfbBuffer to a block missing it · adba7dfc
      Alejandro Piñeiro authored
      If a block has assigned a XfbOffset it is assumed that it would
      inherit the current global XfbBuffer. This commit fixes two use cases:
      
      1) Getting the members of a Block with a XfbOffset to be assigned an
         offset, as explained on GLSL 4.60 spec, section "4.4.2 Output
         Layout Qualifiers", subsection "Transform Feedback Layout
         Qualifiers".
      
      2) Compute properly an error on overlapping ranges if a block is
         assigned a XfbOffset and one of it members is assigned a explicit
         one. This gets working because when the members of a block get
         assigned a Offset/Buffer at fixBlockXfbOffsets, then the block is
         deassigned the Offsets, so ranges are computed only with the block
         members.
      
      BTW, this is already done when redeclaring block builtins.
      
      Fixes #1535
  2. 09 Nov, 2018 2 commits
  3. 08 Nov, 2018 3 commits
  4. 07 Nov, 2018 2 commits
  5. 06 Nov, 2018 1 commit
  6. 02 Nov, 2018 3 commits
    • Merge pull request #1559 from jeffbolznv/glslang_pch · 1c1c2d64
      John Kessenich authored
      Use precompiled headers for some glslang projects (MSVC-only)
    • Merge pull request #1557 from nicebyte/spec-const-decorations · cdf7a85b
      John Kessenich authored
      Add names for composite spec constants in SPIR-V
    • Add names for composite constants in SPIR-V · 4c9876b3
      Grigory Dzhavadyan authored
      Consider the following code:
      
          layout(constant_id=0) const int Y = 1;
          layout(constant_id=1) const int Z = 2;
          layout(constant_id=3) const int X = Y + Z;
      
      Previously, it would produce SPIR-V decorations like this:
      
          Decorate 21(Y) SpecId 1
          Decorate 22 SpecId 3
          Decorate 33(Z) SpecId 0
      
      This seems inaccurate, since the spec constant `X` that is dependent on
      the two others did not get a name in the SPIR-V decorations. This behavior
      may potentially negatively affect shader introspection capabilities.
      
      This change alters the behavior to always add a name, which results in the code
      above producing the following decorations:
      
          Decorate 21(Y) SpecId 1
          Decorate 22(X) SpecId 3
          Decorate 33(Z) SpecId 0
  7. 31 Oct, 2018 4 commits
  8. 30 Oct, 2018 2 commits
  9. 29 Oct, 2018 2 commits
  10. 26 Oct, 2018 6 commits
  11. 25 Oct, 2018 2 commits
  12. 24 Oct, 2018 1 commit
  13. 22 Oct, 2018 1 commit
  14. 21 Oct, 2018 1 commit
  15. 20 Oct, 2018 1 commit
  16. 17 Oct, 2018 3 commits
  17. 16 Oct, 2018 2 commits
  18. 10 Oct, 2018 1 commit
  19. 05 Oct, 2018 2 commits