1. 08 Jun, 2016 3 commits
  2. 07 Jun, 2016 1 commit
  3. 06 Jun, 2016 5 commits
  4. 05 Jun, 2016 3 commits
  5. 04 Jun, 2016 1 commit
  6. 03 Jun, 2016 11 commits
  7. 02 Jun, 2016 3 commits
  8. 01 Jun, 2016 1 commit
  9. 31 May, 2016 2 commits
  10. 30 May, 2016 1 commit
  11. 25 May, 2016 6 commits
  12. 24 May, 2016 3 commits
    • Fix test case for the "empty" linker test case · 0bb546f8
      Thomas Perl authored
      The test result should only give one error about linking
      ES and non-ES shading language compilation units:
      
       - empty.frag: No version info, interpreted as 100, ES
       - empty2.frag: No version info, interpreted as 100, ES
       - empty3.frag: Version declared as 110, non-ES
      
      Previously, because the new intermediate is always created
      without version/profile information, there would be two
      linker errors:
      
       1.) When merging the new intermediate with empty.frag
       2.) When merging (new intermediate + empty.frag + empty2.frag) with empty3.frag
      
      Now, there is only one error; as the error with merging the
      new intermediate with empty.frag has been removed.
    • Use version/profile from first compilation stage · b40a6d6b
      Thomas Perl authored
      When linking multiple compilation units per shader stage,
      the code creates a new intermediate, but fails to set its
      version and profile.
      
      This change makes it so that the new intermediate inherits
      the version and profile of the first compilation unit, so
      that two ES SL compilation units can be combined.