1. 11 Jan, 2019 1 commit
  2. 20 Nov, 2018 1 commit
  3. 25 Oct, 2018 1 commit
  4. 14 Sep, 2018 1 commit
  5. 12 Jul, 2018 1 commit
  6. 21 Jun, 2018 1 commit
  7. 08 Nov, 2017 1 commit
    • 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
  8. 06 Nov, 2017 1 commit
  9. 07 Sep, 2017 1 commit
    • Andreas Haas's avatar
      [wasm] Avoid executing infinite loops in the wasm fuzzers · 7b53a0e0
      Andreas Haas authored
      The wasm-async fuzzer uses the bytes provided by the fuzzer engine
      directly as wasm module bytes, compiles them with async compilation, and
      then tries to execute the "main" function of the module. This "main"
      can have an infinite loop which causes a timeout in the fuzzer. With
      this CL the "main" function is first executed with the interpreter. If
      the execution in the interpreter finishes within 16k steps, which means
      that there is no infinite loop, also the compiled code is executed.
      
      I added the raw fuzzer input as a test case because in this case I
      really want to test the fuzzer and not V8.
      
      R=clemensh@chromium.org
      
      Bug: chromium:761784
      Change-Id: Id1fe5da0da8670ec821ab9979fdb9454dbde1162
      Reviewed-on: https://chromium-review.googlesource.com/651046
      Commit-Queue: Andreas Haas <ahaas@chromium.org>
      Reviewed-by: 's avatarClemens Hammacher <clemensh@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#47874}
      7b53a0e0
  10. 18 Jul, 2017 1 commit
  11. 08 May, 2017 1 commit