1. 20 Jan, 2016 5 commits
  2. 19 Jan, 2016 17 commits
  3. 18 Jan, 2016 6 commits
  4. 17 Jan, 2016 1 commit
  5. 16 Jan, 2016 1 commit
    • Memory/Perf: For link-mode, isolate file I/O so API can be looped over. · c57b2a97
      John Kessenich authored
      Separating file I/O from compile/link lets the compile/link be done
      repeatedly in a loop for testing and measuring of performance and
      memory footprint, including seeing memory growth over time for
      functional-level memory-leak testing.
      
      While the older compile-only mode already had this functionality,
      and typically showed no memory leaks, SPIR-V uses the link path,
      has pending "TODO" for memory freeing, and this shows several
      kilobytes of leaking per compile-link. Most likely, pending
      merge request 131 will address much of this.
  6. 15 Jan, 2016 1 commit
  7. 14 Jan, 2016 6 commits
  8. 12 Jan, 2016 1 commit
  9. 11 Jan, 2016 2 commits
    • Merge branch 'master' of github.com:google/glslang into loopgen · dba28263
      Dejan Mircevski authored
      Change-Id: Ie8236430bb9e30a9be2e0c1573c42183c2f4d0d4
    • Fix back-branch target for do-while loops. · 832c65c3
      Dejan Mircevski authored
      To ensure back branches always go to a header block, create a header
      block even for !testFirst loops.  Then unify common code between the
      testFirst/!testFirst cases.
      
      Generate the header-block code first, so update golden files.
      
      Realize that certain infinite loops generate invalid SPIR-V, so put a
      TODO to instead abort code generation in such cases.
      
      Change-Id: I1e173c8f73daad186cfc666b7d72bd563ed7665d