Skip to content

V
V8
Switch branch/tag
  1. 03 Aug, 2015 1 commit
    • bbudge's avatar
      SIMD.js Add the other SIMD Phase 1 types. · 7b9670b6
      bbudge authored 
      Adds Int32x4, Bool32x4, Int16x8, Bool16x8, Int8x16, Bool8x16.
Adds Simd128Value base heap object class.
Changes heap/factory construction pattern to use arrays.
Adds replaceLane functions to facilitate testing.

NOPRESUBMIT=true
(presubmit checks erroneously interpret array declaration in macro definition as variable size array.)

LOG=Y
BUG=v8:4124

Review URL: https://codereview.chromium.org/1250733005

Cr-Commit-Position: refs/heads/master@{#29974}
      7b9670b6
  3. 31 Jul, 2015 1 commit
    • bmeurer's avatar
      [stubs] Unify (and optimize) implementation of ToObject. · 4fc6f547
      bmeurer authored 
      This is the initial (big) step towards a more uniform implementation of
the ToObject abstract operation (ES6 7.1.13), where we have a fallback
implementation in JSReceiver::ToObject() and a fast (hydrogen) CodeStub
to deal with the fast case (we should be able to do more cleanup on this
in a followup CL).  For natives we expose the abstract operation via a
%_ToObject intrinsic, also exposed via a macro TO_OBJECT, that unifies
the previous confusion with TO_OBJECT_INLINE, ToObject, TO_OBJECT,
$toObject and %$toObject.  Now the whole implementation of the abstract
operation is context independent, meaning we don't need any magic in the
builtins object nor the native context.

R=mvstanton@chromium.org,yangguo@chromium.org

Review URL: https://codereview.chromium.org/1266013006

Cr-Commit-Position: refs/heads/master@{#29953}
      4fc6f547
  5. 28 Jul, 2015 2 commits
  7. 27 Jul, 2015 2 commits
  9. 24 Jul, 2015 4 commits
    • chunyang.dai's avatar
      X87: [stubs] Optimize LoadGlobalViaContextStub and StoreGlobalViaContextStub. · 4c698991
      chunyang.dai authored 
      port d6ee366d (r29834).

original commit message:

    This is the initial round of optimizations for the
    LoadGlobalViaContextStub and StoreGlobalViaContextStub, basically
    turning them into platform code stubs to avoid the Crankshaft overhead
    in the fast case, and making the runtime interface cheaper.

BUG=

Review URL: https://codereview.chromium.org/1258513003

Cr-Commit-Position: refs/heads/master@{#29839}
      4c698991
    • chunyang.dai's avatar
      X87: Unify "runtime-style" IC functions with Runtime intrinsics · 2571c69d
      chunyang.dai authored 
      port bc8041dc (r29811).

original commit message:

    Previous to this CL, ICs used a slightly different code idiom
    to get to C++ code from generated code than runtime intrinsics,
    using an IC_Utility class that in essence provided exactly
    the same functionality as Runtime::FunctionForId, but in its
    own quirky way.

    This CL unifies the two mechanisms, folding IC_Utility
    away by making all IC entry points in C++ code, e.g. IC
    miss handlers, full-fledged runtime intrinsics. This makes
    it possible to eliminate a bunch of ad-hoc declarations and
    adapters that the IC system had to needlessly re-invent.

    As a bonus and the original reason for this yak-shave:
    IC-related C++ runtime functions are now callable from
    TurboFan.

BUG=

Review URL: https://codereview.chromium.org/1252903002

Cr-Commit-Position: refs/heads/master@{#29837}
      2571c69d
    • chunyang.dai's avatar
      X87: HydrogenCodeStubs consume stack arguments via descriptor. · 1359017f
      chunyang.dai authored 
      port 3334b830 (r20813).

original commit message:

    HydrogenCodeStubs consume stack arguments via descriptor.

    All of this is controlled by the CallDescriptor. It's simply the case
    that if you specify less registers than the function arity calls for,
    the rest are assumed to be on the stack.

    Bailout handlers accept these constant stack arguments too.

BUG=

Review URL: https://codereview.chromium.org/1258553002

Cr-Commit-Position: refs/heads/master@{#29836}
      1359017f
    • chunyang.dai's avatar
      X87: Fix pushing of register in CallConstructStub outside frame. · 5cdb1cee
      chunyang.dai authored 
      port 1f295980 (r29787).

original commit message:

    This fixes a recent regression where the register holding the original
    receiver was pushed onto the stack before the internal frame within the
    CallStubInRecordCallTarget helper was created. That in turn confused
    the stack walker when allocations in these stubs failed.

BUG=

Review URL: https://codereview.chromium.org/1247493004

Cr-Commit-Position: refs/heads/master@{#29828}
      5cdb1cee
  11. 23 Jul, 2015 1 commit
  13. 16 Jul, 2015 3 commits
  15. 15 Jul, 2015 2 commits
  17. 13 Jul, 2015 2 commits
  19. 02 Jul, 2015 2 commits
    • verwaest's avatar
      Distinguish slow from fast sloppy arguments · c8211b64
      verwaest authored 
      BUG=v8:4137
LOG=n

Review URL: https://codereview.chromium.org/1221713003

Cr-Commit-Position: refs/heads/master@{#29447}
      c8211b64
    • chunyang.dai's avatar
      X87: Make context register implicit for CallInterfaceDescriptors · 70bb2372
      chunyang.dai authored 
      port 7015fd20 (r29402)

original commit message:

    Up until now the context register was listed explicitly in each stub's
    CallInterfaceDescriptor. This was problematic, because it was listed
    first in the list of register parameters--which is fine for Crankshaft,
    which is more or less built to handle the context as the first
    parameter-- but not ideal for TurboFan, which adds the context at
    the end of all function parameters. Now the context register is no
    longer in the register list and can be handled appropriately by both
    compilers. Specifically, this allows the FunctionType specified for
    each CallInterfaceDescriptor to exactly match the parameter register
    list.

BUG=

Review URL: https://codereview.chromium.org/1216543004

Cr-Commit-Position: refs/heads/master@{#29433}
      70bb2372
  21. 01 Jul, 2015 2 commits
  23. 30 Jun, 2015 1 commit
  25. 19 Jun, 2015 1 commit
  27. 18 Jun, 2015 3 commits
  29. 08 Jun, 2015 1 commit
  31. 02 Jun, 2015 1 commit
  33. 01 Jun, 2015 1 commit
  35. 25 May, 2015 1 commit
  37. 21 May, 2015 1 commit
  39. 19 May, 2015 1 commit
  41. 12 May, 2015 1 commit
  43. 07 May, 2015 1 commit
  45. 06 May, 2015 1 commit
    • chunyang.dai's avatar
      X87: Handle the case when derived constructor is [[Call]]ed with 0 args. · 5f047ff6
      chunyang.dai authored 
      port cf53fed9 (r28242).

original commit message:

    ArgumentsAdaptorStub for derived constructor (the one that needs
    new.target) works in this way:
     - If the constructor is invoked via the Construct stub, we know that
       actual arguments always include new.target. ``arguments`` object
       however should not include a new.target, therefore we remove it.
       We achieve this by decrementing the argument count.
     - If the constructor is invoked as a call, we do not care for a correct
       ``arguments`` array since the constructor will immediately throw on
       entrance.
    The bug is that the call could actually pass 0 actual arguments, but I
    decrement unconditionally :(. The fix is to detect this case and avoid
    decrementing. ``arguments`` is bogus, but it is ok as constructor
    throws.

    Long-term we should just remove mucking about with arguments for
    new.target and just get it from the stack.

BUG=

Review URL: https://codereview.chromium.org/1124063002

Cr-Commit-Position: refs/heads/master@{#28246}
      5f047ff6
  47. 05 May, 2015 1 commit
  49. 04 May, 2015 1 commit
  51. 13 Apr, 2015 1 commit
  53. 09 Apr, 2015 1 commit