1. 19 Jun, 2018 3 commits
  2. 18 Jun, 2018 4 commits
  3. 15 Jun, 2018 2 commits
  4. 14 Jun, 2018 6 commits
  5. 13 Jun, 2018 2 commits
  6. 12 Jun, 2018 4 commits
  7. 11 Jun, 2018 10 commits
  8. 07 Jun, 2018 3 commits
  9. 06 Jun, 2018 5 commits
  10. 05 Jun, 2018 1 commit
    • Kenneth Moreland's avatar
      Add ability to "allocate" implicit storage · e62091a6
      Kenneth Moreland authored
      Previously, it was not possible to call Allocate or Shrink on an
      implicit storage. The reason for this is that the implicit storage does
      not represent any real memory and any attempt to modify it is wrong.
      
      However, there are some rare cases where ArrayHandle will attempt to
      "allocate" the storage even when behaving in a read-only manner. The use
      case this is being created for is when an ArrayHandleImplicit first
      calls ReleaseResources and then calls ReleaseResourcesExecution (or
      anything else that tries to get a control-side portal). In this case,
      the ReleaseResources makes the control side portal invalid and the
      ReleaseResourcesExecution attempts to make it valid again by allocating
      the storage to size 0. This change solves the problem by allowing the
      implicit storage to be "allocated" to something smaller than originally
      created.
      e62091a6