1. 09 Nov, 2017 36 commits
  2. 08 Nov, 2017 4 commits
    • Bill Budge's avatar
      Revert "[Memory] Use OS::Allocate for all OS memory allocations." · 1ea3fd2e
      Bill Budge authored
      This reverts commit 7e78506f.
      
      Reason for revert: Broke Android build on Arm64.
      
      Original change's description:
      > [Memory] Use OS::Allocate for all OS memory allocations.
      > 
      > - Eliminates OS::ReserveRegion and OS::ReserveAlignedRegion.
      > - Changes OS::Allocate to take alignment parameter, reorders parameters
      >   to match page_allocator.
      > - Since the size of memory allocation can be deduced, don't return the
      >   amount of memory allocated.
      > - Changes reservation of aligned address space. Before we would reserve
      >   (size + alignment) rounded up to page size. This is too much, because
      >   maximum misalignment is (alignment - page_size).
      > - On Windows and Cygwin, we release an oversize allocation and
      >   immediately retry at the aligned address in the allocation. If we
      >   lose the address due to a race, we just retry.
      > - Clean up all the calls to OS::Allocate in codegen and tests by adding
      >   helper AllocateSystemPage function (allocation.h) and
      >   AllocateAssemblerBuffer (cctest.h).
      > - Changes 'assm' to 'masm' in some targets for consistency when using
      >   a macro-assembler.
      > 
      > Bug: chromium:756050
      > Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng
      > Change-Id: I306dbe042cc867670fdc935abca29db074b0da71
      > Reviewed-on: https://chromium-review.googlesource.com/749848
      > Commit-Queue: Bill Budge <bbudge@chromium.org>
      > Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
      > Reviewed-by: Hannes Payer <hpayer@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#49235}
      
      TBR=bbudge@chromium.org,hpayer@chromium.org,mlippautz@chromium.org
      
      Change-Id: Ic09de4d63c19746a62e804b1f889817ffaebc330
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Bug: chromium:756050
      Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng
      Reviewed-on: https://chromium-review.googlesource.com/758625Reviewed-by: 's avatarBill Budge <bbudge@chromium.org>
      Commit-Queue: Bill Budge <bbudge@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#49242}
      1ea3fd2e
    • Eric Holk's avatar
      [wasm fuzzer] Require AST fuzzer modules to validate · ea08828b
      Eric Holk authored
      The Wasm AST-based fuzzer is supposed to create valid modules by
      construction. This change adds a CHECK to enforce this property.
      
      Additionally, this change exposed several cases where we were not generating
      valid modules before:
        * Block types did not match up correctly
        * Memory operations could have invalid alignments
        * Storing an i64 could generate an i32 argument incorrectly.
      This CL includes fixes for these issues as well.
      
      Bug: 
      Change-Id: I1aef5532bc880367ec46dc6e79b2d4dbacf2f84b
      Reviewed-on: https://chromium-review.googlesource.com/757129
      Commit-Queue: Eric Holk <eholk@chromium.org>
      Reviewed-by: 's avatarAndreas Haas <ahaas@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#49241}
      ea08828b
    • Junliang Yan's avatar
      [wasm] Fix expected function to match interpreter's function · a4d96612
      Junliang Yan authored
      b % 32 could produce negative results. Therefore, the result
      of the shift could be undefined values.
      
      Bug: 
      Change-Id: I6c2f7201df424735695aa01891d46523e3c5bd12
      Reviewed-on: https://chromium-review.googlesource.com/759079
      Commit-Queue: Junliang Yan <jyan@ca.ibm.com>
      Reviewed-by: 's avatarClemens Hammacher <clemensh@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#49240}
      a4d96612
    • Sathya Gunasekaran's avatar
      [class] Use CreateDataProperty runtime call · 24b26a0c
      Sathya Gunasekaran authored
      StoreDataPropertyInLiteral doesn't throw (because the previous uses of
      this didn't throw), but class fields can throw on defining the
      property which means we can't use this. Changing to CreateDataProperty
      runtime call instead.
      
      Bug: v8:5367
      Change-Id: I1ab45413b121972dd18fe2b35a0cedd8efe0e0bf
      Reviewed-on: https://chromium-review.googlesource.com/757824
      Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org>
      Reviewed-by: 's avatarGeorg Neis <neis@chromium.org>
      Reviewed-by: 's avatarMythri Alle <mythria@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#49239}
      24b26a0c