1. 02 Jul, 2021 1 commit
  2. 01 Jul, 2021 2 commits
  3. 30 Jun, 2021 1 commit
  4. 29 Jun, 2021 3 commits
  5. 28 Jun, 2021 6 commits
  6. 25 Jun, 2021 3 commits
  7. 23 Jun, 2021 1 commit
  8. 21 Jun, 2021 1 commit
  9. 18 Jun, 2021 2 commits
  10. 17 Jun, 2021 2 commits
  11. 16 Jun, 2021 1 commit
  12. 15 Jun, 2021 1 commit
  13. 10 Jun, 2021 2 commits
  14. 08 Jun, 2021 1 commit
  15. 07 Jun, 2021 1 commit
  16. 03 Jun, 2021 3 commits
    • Remove git submodules before rolling into Android · efe254de
      Nicolas Capens authored
      This change adds a script which is to be called by the SwiftShader into
      Android AutoRoller: https://autoroll.skia.org/r/swiftshader-android
      
      It prepares a checkout for upload into the Android repo. Specifically,
      Android does not allow remote submodules, so this script removes them.
      Note SwiftShader does not require any submodules to build the library;
      they are optional for development purposes.
      
      Bug: b/189557997
      Change-Id: I36b4ae59cd843f1c69146f0f52ce8f323c6bc15a
      Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/54768Reviewed-by: 's avatarAlexis Hétu <sugoi@google.com>
      Kokoro-Result: kokoro <noreply+kokoro@google.com>
      Tested-by: 's avatarNicolas Capens <nicolascapens@google.com>
    • Value-initialize all vk::GraphicsState members · 940f2acc
      Nicolas Capens authored
      The vk::GraphicsState constructor does not initialize all members in all
      code paths. We were relying on the zero-initializing done by
      vk::allocate() which is used to allocate vk::GraphicsPipeline which in
      turn contains a GraphicsState member.
      
      We want to change vk::allocate() to no longer zero-initialize all
      memory, to catch more MemorySanitizer errors made by applications. Thus
      we must also not rely on such automatic initialization ourselves.
      
      Note that this change might also hide MemorySantizer violations
      committed by the application side. For example some state is only copied
      from VkGraphicsPipelineCreateInfo into vk::GraphicsState on construction
      when flags indicate they're not dynamic state. If the application
      forgets to makerecord commands that set the dynamic state, their value
      is undefined:
      
      Vulkan 1.2.178 section 6. Command Buffers:
      "When a command buffer begins recording, all state in that command
      buffer is undefined."
      
      Vulkan 1.2.178 section 10.11. Dynamic State:
      "If the state is specified as dynamic in the new pipeline object, then
      that command buffer state is not disturbed. Before any draw or dispatch
      call with this pipeline there must have been at least one call to each
      of the corresponding dynamic state setting commands since the command
      buffer recording was begun, or the last bound pipeline object with that
      state specified as static, whichever was the latter."
      
      Thus once sw::allocate() no longer also zeroes this data, we should
      revert the value-initialization where possible and ensure we don't
      touch the uninitialized data ourselves, unless as a consequence of an
      application bug.
      
      Bug: b/140991626
      Change-Id: I060e8d8a79e93b0676669eed361fab4f86ab1b56
      Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/53089
      Presubmit-Ready: Nicolas Capens <nicolascapens@google.com>
      Kokoro-Result: kokoro <noreply+kokoro@google.com>
      Tested-by: 's avatarNicolas Capens <nicolascapens@google.com>
      Reviewed-by: 's avatarAlexis Hétu <sugoi@google.com>
    • Explicitly initialize VkSpecializationInfo fields · 491ade49
      Nicolas Capens authored
      vk::allocate() zero-initializes its memory, which was nulling the
      VkSpecializationInfo::pMapEntries field in case the mapEntryCount is 0.
      
      We'll be changing vk::allocate() to not zero-initialize, to catch cases
      where applications might incorrectly be relying on it, with
      MemorySanitizer. So we have to also not be relying on it.
      
      Bug: b/140991626
      Change-Id: I5917c902c0af27985556340dfc1dbae79010a125
      Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/54468
      Presubmit-Ready: Nicolas Capens <nicolascapens@google.com>
      Kokoro-Result: kokoro <noreply+kokoro@google.com>
      Tested-by: 's avatarNicolas Capens <nicolascapens@google.com>
      Reviewed-by: 's avatarAlexis Hétu <sugoi@google.com>
  17. 02 Jun, 2021 2 commits
  18. 31 May, 2021 1 commit
  19. 29 May, 2021 2 commits
  20. 27 May, 2021 4 commits