1. 04 Aug, 2017 3 commits
  2. 02 Aug, 2017 1 commit
  3. 01 Aug, 2017 1 commit
  4. 31 Jul, 2017 7 commits
  5. 29 Jul, 2017 2 commits
  6. 28 Jul, 2017 3 commits
  7. 27 Jul, 2017 2 commits
  8. 26 Jul, 2017 3 commits
    • Merge pull request #997 from LoopDawg/clipcull-semantic · f1f5058a
      John Kessenich authored
      HLSL: handle multiple clip/cull semantic IDs
    • HLSL: handle multiple clip/cull semantic IDs · 307b6507
      LoopDawg authored
      HLSL allows several variables to be declared.  There are packing rules involved:
      e.g, a float3 and a float1 can be packed into a single array[4], while for a
      float3 and another float3, the second one will skip the third array entry to
      avoid straddling
      
      This is implements that ability.  Because there can be multiple variables involved,
      and the final output array will often be a different type altogether (to fuse
      the values into a single destination), a new variable is synthesized, unlike the prior
      clip/cull support which used the declared variable.  The new variable name is
      taken from one of the declared ones, so the old tests are unchanged.
      
      Several new tests are added to test various packing scenarios.
      
      Only two semantic IDs are supported: 0, and 1, per HLSL rules.  This is
      encapsulated in
      
           static const int maxClipCullRegs = 2;
      
      and the algorithm (probably :) ) generalizes to larger values, although there
      are a few issues around how HLSL would pack (e.g, would 4 scalars be packed into
      a single HLSL float4 out reg?  Probably, and this algorithm assumes so).
  9. 25 Jul, 2017 2 commits
  10. 23 Jul, 2017 2 commits
  11. 21 Jul, 2017 2 commits
  12. 20 Jul, 2017 1 commit
  13. 18 Jul, 2017 4 commits
  14. 16 Jul, 2017 3 commits
  15. 15 Jul, 2017 1 commit
  16. 14 Jul, 2017 2 commits
  17. 13 Jul, 2017 1 commit
    • Address part A of #982: $Global will use std140 instead of HLSL offsets. · 735d7e56
      John Kessenich authored
      From comment about this:
      Adjust alignment for HLSL rules
      TODO: make this consistent in early phases of code: adjusting this late means inconsistencies with earlier code, which for reflection is an issue.
      Until reflection is brought in sync with these adjustments, don't apply to $Global,
      which is the most likely to rely on reflection, and least likely to rely
      implicit layouts.