1. 28 Feb, 2017 5 commits
  2. 27 Feb, 2017 6 commits
  3. 24 Feb, 2017 2 commits
  4. 23 Feb, 2017 2 commits
  5. 22 Feb, 2017 6 commits
  6. 21 Feb, 2017 4 commits
  7. 20 Feb, 2017 6 commits
  8. 19 Feb, 2017 1 commit
  9. 18 Feb, 2017 2 commits
    • vabr's avatar
      Fix typeof optimization for undetectable · 6302753e
      vabr authored
      Currently, typeof o, where o is an undetectable
      callable object (such as document.all), returns 'function' if
      optimised. It should, however, return 'undefined'.
      
      This CL excludes undetectable objects from the optimization
      resulting in type 'function' and renames the related code to
      reflect that.
      
      BUG=v8:5972
      R=bmeurer@chromium.org
      
      Review-Url: https://codereview.chromium.org/2697063002
      Cr-Commit-Position: refs/heads/master@{#43298}
      6302753e
    • mtrofin's avatar
      [wasm] Embedder can control what buffers wasm compilation works on. · d9bc0ffb
      mtrofin authored
      Two controls, one for instantiation and one for compilation. They allow
      the embedder (e.g. Chrome) check properties of the parameters of those
      two operations, and decide if they are allowed to continue.
      
      For example, Chrome may now decline compilation of certain size buffers,
      in synchronous cases; same for instantiation (where the buffer size
      refers to the size of the buffer containing wasm wire bytes)
      
      BUG=v8:5981
      
      Review-Url: https://codereview.chromium.org/2699843003
      Cr-Commit-Position: refs/heads/master@{#43295}
      d9bc0ffb
  10. 17 Feb, 2017 3 commits
  11. 16 Feb, 2017 3 commits
    • jwolfe's avatar
      Implement new Function.prototype.toString --harmony-function-tostring · d1d4b9ce
      jwolfe authored
      For functions declared in source code, the .toString() representation
      will be an excerpt of the source code.
      * For functions declared with the "function" keyword, the excerpt
        starts at the "function" or "async" keyword and ends at the final "}".
        The previous behavior would start the excerpt at the "(" of the
        parameter list, and prepend a canonical `"function " + name` or
        similar, which would discard comments and formatting surrounding the
        function's name. Anonymous functions declared as function expressions
        no longer get the name "anonymous" in their toString representation.
      * For methods, the excerpt starts at the "get", "set", "*" (for
        generator methods), or property name, whichever comes first.
        Previously, the toString representation for methods would use a
        canonical prefix before the "(" of the parameter list. Note that any
        "static" keyword is omitted.
      * For arrow functions and class declarations, the excerpt is unchanged.
      
      For functions created with the Function, GeneratorFunction, or
      AsyncFunction constructors:
      * The string separating the parameter text and body text is now
        "\n) {\n", where previously it was "\n/*``*/) {\n" or ") {\n".
      * At one point, newline normalization was required by the spec here,
        but that was removed from the spec, and so this CL does not do it.
      
      Included in this CL is a fix for CreateDynamicFunction parsing. ')'
      and '`' characters in the parameter string are no longer disallowed,
      and Function("a=function(", "}){") is no longer allowed.
      
      BUG=v8:4958, v8:4230
      
      Review-Url: https://codereview.chromium.org/2156303002
      Cr-Commit-Position: refs/heads/master@{#43262}
      d1d4b9ce
    • gsathya's avatar
      [mjsunit] Exit on hitting unreachable code instead of throwing · 7ee77b9b
      gsathya authored
      Errors are swallowed by promises, so just exit with stack trace.
      
      Review-Url: https://codereview.chromium.org/2693383004
      Cr-Commit-Position: refs/heads/master@{#43254}
      7ee77b9b
    • mvstanton's avatar
      This is a workaround for the fact that %SetCode can "lose" the script for a js... · ae8f2820
      mvstanton authored
      This is a workaround for the fact that %SetCode can "lose" the script for a js native. If the js native is re-initialized (for a Realm or something), then the source SharedFunctionInfo won't have a script anymore. Nonetheless, we may want to optimize the function. If we've compiled bytecode, then we can compile optimized code without a script.
      
      Here, we carve out a special exception for this case, so that we can turn on the --mark-shared-functions-for-tier-up.
      
      BUG=v8:5946
      R=leszeks@chromium.org
      
      Review-Url: https://codereview.chromium.org/2684033007
      Cr-Original-Commit-Position: refs/heads/master@{#43240}
      Committed: https://chromium.googlesource.com/v8/v8/+/4123a3dd790495c40cf839990318a85c146e057d
      Review-Url: https://codereview.chromium.org/2684033007
      Cr-Commit-Position: refs/heads/master@{#43252}
      ae8f2820