1. 05 Jan, 2021 1 commit
  2. 16 Oct, 2020 1 commit
  3. 15 Oct, 2020 1 commit
  4. 27 Mar, 2020 1 commit
    • Clemens Backes's avatar
      [wasm][debug] Fix printing of wasm opcodes · a1d2e342
      Clemens Backes authored
      This is a minor cosmetic fix. Wasm opcodes are bytes, hence they should
      always be printed as an even number of hexadecimal digits.
      Note that currently we only print a single byte anyway, but in the
      future we will want to extend this to correctly parse multi-byte
      opcodes. Those will also be printed as an even number of characters
      then.
      
      R=thibaudm@chromium.org
      
      Bug: v8:10351
      Change-Id: I2423277b470d74c1c72cb619c2a43bb978423bc0
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2122025Reviewed-by: 's avatarThibaud Michaud <thibaudm@chromium.org>
      Commit-Queue: Clemens Backes <clemensb@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#66883}
      a1d2e342
  5. 26 Mar, 2020 1 commit
  6. 25 Mar, 2020 3 commits
  7. 24 Mar, 2020 1 commit
    • Clemens Backes's avatar
      [wasm] Fix OSR on wasm calls · 851a395f
      Clemens Backes authored
      This fixes issues with replacing the return address of deeper (non-top)
      wasm frames, i.e. frames which are at a call position. The replaced
      address should also point after the call in the new code, so we don't
      execute the same call again.
      
      This is achieved by using slightly different encodings for breakpoint
      positions and other (wasm instruction) positions. Breakpoints set
      {is_instruction} to {false} in the source position table entry, whereas
      usual wasm instruction set it to {true}.
      Also, during stack walking for OSR, we remember whether we want to OSR
      to the position before the instruction (if it's the top frame), or after
      the call instruction (if it's deeper in the stack). We then use the
      {is_instruction} predicate to find the right location.
      
      R=thibaudm@chromium.org
      
      Bug: v8:10321
      Change-Id: I73212a7532c6ecf4c82bde76fe4059c8203e422c
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2116206Reviewed-by: 's avatarThibaud Michaud <thibaudm@chromium.org>
      Commit-Queue: Clemens Backes <clemensb@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#66850}
      851a395f
  8. 19 Mar, 2020 1 commit
  9. 17 Mar, 2020 1 commit
  10. 13 Mar, 2020 2 commits