1. 19 Feb, 2019 2 commits
  2. 15 Feb, 2019 23 commits
  3. 14 Feb, 2019 1 commit
  4. 13 Feb, 2019 1 commit
  5. 12 Feb, 2019 2 commits
  6. 11 Feb, 2019 6 commits
  7. 08 Feb, 2019 2 commits
  8. 06 Feb, 2019 3 commits
    • Basic DescriptorPool and DescriptorSetLayout implementation · c8176632
      Alexis Hetu authored
      This cl is a minimal implementation of DescriptorPool and
      DescriptorSetLayout.
      
      A DescriptorSet itself is just a straight memory pointer.
      
      A DescriptorPool is a memory pool where DescriptorSets are
      allocated. The DescriptorPool object itself is little more
      than a memory allocator.
      A few minor optimizations were made to speed up the default
      case:
      - The Descriptor pool starts looking for a large enough
        memory block at the end of the pool, which should be optimal
        if the DescriptorSets are allocated linearly
      - When allocating multiple DescriptorSets at once, the pool
        first attempts to allocated all of them contiguously. This
        prevents looking for free memory blocks multiple times and
        once again should be optimal if the DescriptorSets are
        allocated linearly
      
      Note: For now, DescriptorSetLayout::GetDescriptorSize() is a
            dummy function which always returns the same size for
            every Descriptor type. This will be implemented properly
            case by case as we add support for new Descriptor types.
      
      Passes all tests in:
      dEQP-VK.api.*descriptor*
      
      Bug b/123244275
      
      Change-Id: I2a2e73396e38dae28b59b77243cd8a366b35c12c
      Reviewed-on: https://swiftshader-review.googlesource.com/c/24028Tested-by: 's avatarAlexis Hétu <sugoi@google.com>
      Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
      Reviewed-by: 's avatarChris Forbes <chrisforbes@google.com>
    • Add SPIRV-Tools to the Vulkan build. · a69ca605
      Nicolas Capens authored
      Bug b/123642959
      
      Change-Id: I8edc9ac199b2d212b9e563dcc31f9f46757ed596
      Reviewed-on: https://swiftshader-review.googlesource.com/c/24351Tested-by: 's avatarNicolas Capens <nicolascapens@google.com>
      Reviewed-by: 's avatarChris Forbes <chrisforbes@google.com>
      Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
    • Add Visual Studio project files for SPIRV-Tools. · 4c9f04bb
      Nicolas Capens authored
      SPIRV-Tools comes with CMake build files. Integrating it into our
      custom Visual Studio solution requires making the project files that
      it generates path independent so that they can be checked into the
      repository.
      
      This is achieved by the build/cmake.sh shell script that is intended
      to be run from the Git Bash shell. It needs to be re-run when any
      CMakeLists.txt file changes.
      
      .gitignore was modified to allow for build files under the build/
      directory to be checked in. CMakeFiles/ and CMakeCache.txt are ignored
      because they contain absolute paths and aren't necessary for building.
      
      Bug b/123642959
      
      Change-Id: I0706e3302d16144ecb9c0802cec897aa66affe6f
      Reviewed-on: https://swiftshader-review.googlesource.com/c/24349Tested-by: 's avatarNicolas Capens <nicolascapens@google.com>
      Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
      Reviewed-by: 's avatarChris Forbes <chrisforbes@google.com>