1. 01 Jun, 2021 1 commit
  2. 22 Mar, 2021 1 commit
  3. 14 Jan, 2021 1 commit
  4. 08 Oct, 2019 1 commit
  5. 30 Jan, 2019 1 commit
  6. 29 Oct, 2018 1 commit
  7. 29 Aug, 2017 1 commit
    • Enrico Bacis's avatar
      [wasm] Add tests for grow_memory in functions inside loops · 08e8bbaf
      Enrico Bacis authored
      This CL introduces 4 test that verify that the effects of a grow_memory
      instruction executed in a function invoked inside a loop are visible
      also when the loop is over. This is needed because the
      AnalyzeLoopAssignment method in function-body-decoder.cc is creating Phi
      nodes only for variables assigned inside the loop. The test cases
      introduced by this CL verify that the mem_size and mem_start variables
      are always correct.
      
      The tests verify the output of the current_memory instruction and the
      result of loading a variable stored in the grown memory inside the
      loop in the following cases:
      
       * the memory is grown in a directly called function inside a loop;
      
       * the memory is grown in an indirectly called function inside a loop.
      
      R=ahaas@chromium.org,clemensh@chromium.org,gdeepti@chromium.org
      
      Change-Id: I2992bf4086b5eac9580c87e2e0ca06364b99714c
      Reviewed-on: https://chromium-review.googlesource.com/637911Reviewed-by: 's avatarAndreas Haas <ahaas@chromium.org>
      Reviewed-by: 's avatarDeepti Gandluri <gdeepti@chromium.org>
      Commit-Queue: Enrico Bacis <enricobacis@google.com>
      Cr-Commit-Position: refs/heads/master@{#47674}
      08e8bbaf
  8. 17 Aug, 2017 1 commit
    • Enrico Bacis's avatar
      [wasm] Add tests for grow_memory inside functions · d74ec7ef
      Enrico Bacis authored
      This CL introduces 6 tests that verify that the effects of a grow_memory
      instruction executed inside a function are visible also from the caller of
      the function.
      
      The tests verify that:
      
       * the current_memory instruction returns the correct value after
       returning from a function that grew memory;
      
       * accessing a memory page that has been created inside a function does
       not trap in the caller;
      
       * when a function grows the memory and then store something in the grown
       memory, the caller always reads from the grown memory. This checks that
       the memory start address gets updated in the caller (the memory buffer
       could in fact be relocated by the grow_memory instruction).
      
      These tests are implemented for direct and indirect function calls.
      
      R=ahaas@chromium.org,clemensh@chromium.org
      
      Change-Id: Iac8db0fa7a6dd6f530e090af5423fc165d87e863
      Reviewed-on: https://chromium-review.googlesource.com/616150
      Commit-Queue: Enrico Bacis <enricobacis@google.com>
      Reviewed-by: 's avatarAndreas Haas <ahaas@chromium.org>
      Reviewed-by: 's avatarDeepti Gandluri <gdeepti@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#47398}
      d74ec7ef