1. 09 Sep, 2016 4 commits
    • bmeurer's avatar
      [turbofan] Initial support for polymorphic inlining. · 7d4ab7d4
      bmeurer authored
      For call sites where the target is not a known constant, but potentially
      a list of known constants (i.e. a Phi with all HeapConstant inputs), we
      still record the call site as a potential candidate for inlining.
      In case the heuristic picks that candidate for inlining, we
      expand the call site to a dispatched call site and invoke the
      actual inlining logic for all the nested call sites.
      
      Like Crankshaft, we currently allow up to 4 targets for polymorphic inlining,
      although we might want to refine that later.
      
      This approach is different from what Crankshaft does in
      that we don't duplicate the evaluation of the parameters per polymorphic
      case. Instead we first perform the load of the target (which usually
      dispatches based on the receiver map), then we evaluate all the
      parameters, and then we dispatch again based on the known targets. This
      might generate better or worse code compared to what Crankshaft does,
      and for the cases where we generate worse code (i.e. because we have
      only trivial parameters or no parameters at all), we might want to
      investigate optimizing away the double dispatch in the
      future.
      
      R=mvstanton@chromium.org
      BUG=v8:5267,v8:5365
      
      Review-Url: https://codereview.chromium.org/2325943002
      Cr-Commit-Position: refs/heads/master@{#39302}
      7d4ab7d4
    • machenbach's avatar
      [test] Fix the noi18n trybot · bcc3cb2e
      machenbach authored
      This is a work-around as v8_enable_i18n_support=false does
      currently not imply icu_use_data_file_flag=false. The
      swarming isolator then tries to find the data file also
      in builds without ICU.
      
      Making the implication is non-trivial as icu_use_data_file_flag lives
      in ICU and v8_enable_i18n_support lives in V8.
      
      BUG=chromium:474921
      NOTRY=true
      TBR=petermarshall@chromium.org, vogelheim@chromium.org, jochen@chromium.org
      
      Review-Url: https://codereview.chromium.org/2321563007
      Cr-Commit-Position: refs/heads/master@{#39301}
      bcc3cb2e
    • marja's avatar
      Move ParseHoistableDeclaration to ParserBase. · 751f8e99
      marja authored
      BUG=
      
      Review-Url: https://codereview.chromium.org/2311903003
      Cr-Commit-Position: refs/heads/master@{#39300}
      751f8e99
    • zhengxing.li's avatar
      X87: [Interpreter] Collect allocation site feedback in call bytecode handler. · 1d2574af
      zhengxing.li authored
        port 9a31162d(r39283)
      
        original commit message:
        Adds support to collect allocation site feedback for Array function calls
        to the call bytecode handler.
      
      BUG=
      
      Review-Url: https://codereview.chromium.org/2319123004
      Cr-Commit-Position: refs/heads/master@{#39299}
      1d2574af
  2. 08 Sep, 2016 36 commits