Skip to content

V
V8
Switch branch/tag
  1. 09 Nov, 2021 1 commit
  3. 01 Nov, 2021 1 commit
  5. 26 Oct, 2021 1 commit
  7. 20 Oct, 2021 1 commit
    • Milad Fa's avatar
      PPC/s390: [turbofan] Handle class constructor · d219d39a
      Milad Fa authored 
      Port e127f584

Original Commit Message:

    Handling of class constructors was moved from CallFunction to Call
    in [1].
    When reducing calls with spread we forward varargs directly to
    CallFunction, if we are spreading to inlined arguments or arguments of
    the outermost function.
    In that case we didn't check for class constructors and therefore didn't
    raise an exception.
    This CL adds checks for class constructors to all JSCall* nodes in
    JSCallReducer that missed them before.

    [1] https://crrev.com/c/3186434

R=pthier@chromium.org, joransiu@ca.ibm.com, junyan@redhat.com, midawson@redhat.com
BUG=
LOG=N

Change-Id: I02cba90369354f064201daa1bf8812e17cb2dc21
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3234040Reviewed-by: 's avatarJunliang Yan <junyan@redhat.com>
Commit-Queue: Milad Fa <mfarazma@redhat.com>
Cr-Commit-Position: refs/heads/main@{#77480}
      d219d39a
  9. 30 Sep, 2021 1 commit
  11. 29 Sep, 2021 1 commit
    • Milad Fa's avatar
      PPC/s390: Create Instance Type for Class Constructors · 7245d2c1
      Milad Fa authored 
      Port: 1cd7a582

Original Commit Message:

Class Constructors are special, because they are callable but [[Call]]
raises an exception. Instead of checking if a JS function is a class
constructor for every JS function call, this CL adds a new instance
type for class constructors.
This way we can use a fast instance type range check for the common
case, and only check for class constructors in the uncommon case were
a class constructor is called and when we need to raise an exception.

Change-Id: I578fde90d00d1e80cf36ba28205ce9bfe6830afb
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3192422Reviewed-by: 's avatarJunliang Yan <junyan@redhat.com>
Commit-Queue: Milad Fa <mfarazma@redhat.com>
Cr-Commit-Position: refs/heads/main@{#77147}
      7245d2c1
  13. 07 Sep, 2021 1 commit
    • Milad Fa's avatar
      PPC/s390: [sparkplug] Remove BaselineData, use Code directly · 0100a8e8
      Milad Fa authored 
      Port 787bec09

Original Commit Message:

    Remove the BaselineData intermediate structure for baseline code, and
    write the baseline Code object into the SharedFunctionInfo directly. We
    still need a pointer to the BytecodeArray/InterpreterData, so re-use the
    Code object's deoptimization data slot for this (baseline code doesn't
    have deoptimization data).

    A consequence of this is that the BytecodeArray pointer becomes
    immutable when there is baseline code. This means that we cannot install
    a debug BytecodeArray while baseline code is active (we have to flush it
    first), and we can't tier-up code with debug BytecodeArray to baseline.

R=leszeks@chromium.org, joransiu@ca.ibm.com, junyan@redhat.com, midawson@redhat.com
BUG=
LOG=N

Change-Id: I7e0f7d964341774340d27f1890cef4c7d9ee9dda
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3145171Reviewed-by: 's avatarLeszek Swirski <leszeks@chromium.org>
Commit-Queue: Milad Fa <mfarazma@redhat.com>
Cr-Commit-Position: refs/heads/main@{#76694}
      0100a8e8
  15. 12 Aug, 2021 1 commit
  17. 04 Aug, 2021 1 commit
  19. 26 Jul, 2021 1 commit
  21. 23 Jul, 2021 1 commit
  23. 19 Jul, 2021 2 commits
  25. 07 Jul, 2021 2 commits
  27. 30 Jun, 2021 1 commit
  29. 28 Jun, 2021 1 commit
  31. 24 Jun, 2021 4 commits
  33. 21 Jun, 2021 2 commits
  35. 18 Jun, 2021 1 commit
  37. 16 Jun, 2021 1 commit
    • Milad Fa's avatar
      PPC/S390: Introduce MultiPush/Pop of doubles and/or Simd registers · df912633
      Milad Fa authored 
      When pushing/popping registers, we need a way in PPC and S390
to detect if Simd registers need to be pushed or not.

On PPC Simd registers are separate from FP registers, hence we
need to push them both. If Simd is not available then we push
an empty space in place of Simd registers.

On S390 the Simd and FP registers are shared. If Simd is available
then we only push them and not the FPs, else we push FP registers
as well as an empty space the size of FPs as the stack needs to look
like as if Simds were saved too.

We also need to check if we are generating builtins or
call is being made at runtime. We cannot use `SupportsWasmSimd128`
when generating builtin as `CpuFeatures` are turned off, so we need
to emit the `if/else` manually for checking the value of
`SupportsWasmSimd128`.


Change-Id: Id149c6578db9c2f92d903fd871d85c648d43ce70
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2958963Reviewed-by: 's avatarJunliang Yan <junyan@redhat.com>
Commit-Queue: Milad Fa <mfarazma@redhat.com>
Cr-Commit-Position: refs/heads/master@{#75188}
      df912633
  39. 14 Jun, 2021 1 commit
  41. 11 Jun, 2021 1 commit
  43. 07 Jun, 2021 1 commit
  45. 02 Jun, 2021 1 commit
  47. 01 Jun, 2021 2 commits
  49. 26 May, 2021 1 commit
  51. 25 May, 2021 2 commits
  53. 20 May, 2021 1 commit
  55. 19 May, 2021 3 commits
  57. 17 May, 2021 1 commit
  59. 12 May, 2021 1 commit