1. 10 Mar, 2016 34 commits
  2. 09 Mar, 2016 6 commits
    • mbrandy's avatar
      PPC: [undetectable] Really get comparisons of document.all right now. · eaa38ad1
      mbrandy authored
      Port 679d9503
      
      Original commit message:
          According to https://www.w3.org/TR/html5/obsolete.html#dom-document-all,
          comparisons of document.all to other values such as strings or objects,
          are unaffected. In fact document.all only gets special treatment in
          comparisons with null or undefined according to HTML. Especially setting
          the undetectable doesn't make two distinct JSReceivers equal.
      
      R=bmeurer@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com
      BUG=
      
      Review URL: https://codereview.chromium.org/1785503002
      
      Cr-Commit-Position: refs/heads/master@{#34645}
      eaa38ad1
    • mbrandy's avatar
      PPC: [turbofan] [deoptimizer] Support inlining of ES6 tail calls. · 209c2152
      mbrandy authored
      Port c29a4560
      
      Original commit message:
          In case when F was called with incompatible number of arguments (and therefore
          the arguments adator frame was created), F inlines a tail call of G which then
          deopts the deoptimizer should also remove the arguments adaptor frame for F.
      
          This CL adds required machinery to the deoptimizer.
      
      R=ishell@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com
      BUG=v8:4698
      LOG=N
      
      Review URL: https://codereview.chromium.org/1775393004
      
      Cr-Commit-Position: refs/heads/master@{#34644}
      209c2152
    • mbrandy's avatar
      PPC: [runtime] Unify and simplify how frames are marked · 4445c095
      mbrandy authored
      Port 9dcd0857
      
      Original commit message:
          Before this CL, various code stubs used different techniques
          for marking their frames to enable stack-crawling and other
          access to data in the frame. All of them were based on a abuse
          of the "standard" frame representation, e.g. storing the a
          context pointer immediately below the frame's fp, and a
          function pointer after that. Although functional, this approach
          tends to make stubs and builtins do an awkward, unnecessary
          dance to appear like standard frames, even if they have
          nothing to do with JavaScript execution.
      
          This CL attempts to improve this by:
      
          * Ensuring that there are only two fundamentally different
            types of frames, a "standard" frame and a "typed" frame.
            Standard frames, as before, contain both a context and
            function pointer. Typed frames contain only a minimum
            of a smi marker in the position immediately below the fp
            where the context is in standard frames.
          * Only interpreted, full codegen, and optimized Crankshaft and
            TurboFan JavaScript frames use the "standard" format. All
            other frames use the type frame format with an explicit
            marker.
          * Typed frames can contain one or more values below the
            type marker. There is new magic macro machinery in
            frames.h that simplifies defining the offsets of these fields
            in typed frames.
          * A new flag in the CallDescriptor enables specifying whether
            a frame is a standard frame or a typed frame. Secondary
            register location spilling is now only enabled for standard
            frames.
          * A zillion places in the code have been updated to deal with
            the fact that most code stubs and internal frames use the
            typed frame format. This includes changes in the
            deoptimizer, debugger, and liveedit.
          * StandardFrameConstants::kMarkerOffset is deprecated,
            (CommonFrameConstants::kContextOrFrameTypeOffset
            and StandardFrameConstants::kFrameOffset are now used
            in its stead).
      
      R=danno@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com
      BUG=
      
      Review URL: https://codereview.chromium.org/1778713002
      
      Cr-Commit-Position: refs/heads/master@{#34643}
      4445c095
    • mbrandy's avatar
      PPC: Fix "Rework CallApi*Stubs". · 50e43bc3
      mbrandy authored
      R=joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com
      BUG=
      
      Review URL: https://codereview.chromium.org/1779803004
      
      Cr-Commit-Position: refs/heads/master@{#34642}
      50e43bc3
    • titzer's avatar
      [wasm] Encode function signatures, bodies, and names as separate sections. · 4cb568ec
      titzer authored
      R=binji@chromium.org
      BUG=
      
      Review URL: https://codereview.chromium.org/1783593002
      
      Cr-Commit-Position: refs/heads/master@{#34641}
      4cb568ec
    • adamk's avatar
      Expose Array.prototype.values behind a flag and stage it · c48c1736
      adamk authored
      BUG=v8:4247
      LOG=y
      
      Review URL: https://codereview.chromium.org/1781573003
      
      Cr-Commit-Position: refs/heads/master@{#34640}
      c48c1736