1. 07 Aug, 2015 1 commit
  2. 22 Jul, 2015 1 commit
  3. 16 Jul, 2015 1 commit
  4. 26 Jun, 2015 1 commit
  5. 25 Jun, 2015 1 commit
  6. 04 Jun, 2015 2 commits
    • arv's avatar
      Refactor lexical home object binding · 345fa142
      arv authored
      Before this we had 3 super related lexical bindings that got injected
      into method bodies: .home_object, .this_function,  and new.target.
      With this change we get rid of the .home_object one in favor of using
      .this_function[home_object_symbol] which allows some simplifications
      throughout the code base.
      
      BUG=v8:3768
      LOG=N
      R=adamk@chromium.org, wingo@igalia.com
      
      Review URL: https://codereview.chromium.org/1154103005
      
      Cr-Commit-Position: refs/heads/master@{#28802}
      345fa142
    • mbrandy's avatar
      Add support for Embedded Constant Pools for PPC and Arm · eac7f046
      mbrandy authored
      Embed constant pools within their corresponding Code
      objects.
      
      This removes support for out-of-line constant pools in favor
      of the new approach -- the main advantage being that it
      eliminates the need to allocate and manage separate constant
      pool array objects.
      
      Currently supported on PPC and ARM.  Enabled by default on
      PPC only.
      
      This yields a 6% improvment in Octane on PPC64.
      
      R=bmeurer@chromium.org, rmcilroy@chromium.org, michael_dawson@ca.ibm.com
      BUG=chromium:478811
      LOG=Y
      
      Review URL: https://codereview.chromium.org/1162993006
      
      Cr-Commit-Position: refs/heads/master@{#28801}
      eac7f046
  7. 03 Jun, 2015 1 commit
  8. 02 Jun, 2015 1 commit
    • mbrandy's avatar
      Add support for Embedded Constant Pools for PPC and Arm · a9404029
      mbrandy authored
      Embed constant pools within their corresponding Code
      objects.
      
      This removes support for out-of-line constant pools in favor
      of the new approach -- the main advantage being that it
      eliminates the need to allocate and manage separate constant
      pool array objects.
      
      Currently supported on PPC and ARM.  Enabled by default on
      PPC only.
      
      This yields a 6% improvment in Octane on PPC64.
      
      R=danno@chromium.org, svenpanne@chromium.org, bmeurer@chromium.org, rmcilroy@chromium.org, dstence@us.ibm.com, michael_dawson@ca.ibm.com
      BUG=chromium:478811
      LOG=Y
      
      Review URL: https://codereview.chromium.org/1131783003
      
      Cr-Commit-Position: refs/heads/master@{#28770}
      a9404029
  9. 26 May, 2015 1 commit
    • arv's avatar
      [es6] Support super.property in eval and arrow functions · 44e98103
      arv authored
      When we enter a method that needs access to the [[HomeObject]]
      we allocate a local variable `.home_object` and assign it the
      value from the [[HomeObject]] private symbol. Something along
      the lines of:
      
        method() {
          var .home_object = %ThisFunction()[home_object_symbol];
          ...
        }
      
      BUG=v8:3867, v8:4031
      LOG=N
      
      Review URL: https://codereview.chromium.org/1135243004
      
      Cr-Commit-Position: refs/heads/master@{#28644}
      44e98103
  10. 22 May, 2015 1 commit
  11. 21 May, 2015 2 commits
  12. 19 May, 2015 1 commit
  13. 18 May, 2015 2 commits
  14. 15 May, 2015 1 commit
  15. 05 Mar, 2015 1 commit
  16. 12 Feb, 2015 1 commit
  17. 09 Feb, 2015 1 commit
  18. 06 Feb, 2015 1 commit
    • adamk's avatar
      Add basic compilation support for modules · 70079dab
      adamk authored
      This adds an "experimental" API hook (v8::ScriptCompiler::CompileModule)
      allowing compilation of modules. The code gen is incredibly basic: the
      module body is represented by a Block in the AST. But this at least gets
      more of the pipeline working, and opens the door to writing mjsunit tests
      (once d8 is modified to support module compilation).
      
      BUG=v8:1569
      LOG=n
      
      Review URL: https://codereview.chromium.org/902093002
      
      Cr-Commit-Position: refs/heads/master@{#26496}
      70079dab
  19. 04 Feb, 2015 1 commit
  20. 29 Jan, 2015 3 commits
  21. 27 Nov, 2014 1 commit
  22. 14 Nov, 2014 1 commit
  23. 20 Oct, 2014 1 commit
  24. 10 Sep, 2014 1 commit
  25. 26 Aug, 2014 1 commit
  26. 21 Jul, 2014 1 commit
  27. 16 Jul, 2014 1 commit
    • vogelheim@chromium.org's avatar
      Change ScriptCompiler::CompileOptions to allow for two 'cache' modes · a42612b4
      vogelheim@chromium.org authored
      (parser or code) and to be explicit about cache consumption or production
      (rather than making presence of cached_data imply one or the other.)
      
      Also add a --cache flag to d8, to allow testing the functionality.
      
      -----------------------------
      API change
      
      Reason: Currently, V8 supports a 'parser cache' for repeatedly executing the same script. We'd like to add a 2nd mode that would cache code, and would like to let the embedder decide which mode they chose (if any).
      
      Note: Previously, the 'use cached data' property was implied by the presence of the cached data itself. (That is, kNoCompileOptions and source->cached_data != NULL.) That is no longer sufficient, since the presence of data is no longer sufficient to determine /which kind/ of data is present.
      
      Changes from old behaviour:
      
      - If you previously didn't use caching, nothing changes.
      Example:
        v8::CompileUnbound(isolate, source, kNoCompileOptions);
      
      - If you previously used caching, it worked like this:
      
        - 1st run:
        v8::CompileUnbound(isolate, source, kProduceToCache);
        Then, source->cached_data would contain the
        data-to-be cached. This remains the same, except you
        need to tell V8 which type of data you want.
        v8::CompileUnbound(isolate, source, kProduceParserCache);
      
        - 2nd run:
        v8::CompileUnbound(isolate, source, kNoCompileOptions);
        with source->cached_data set to the data you received in
        the first run. This will now ignore the cached data, and
        you need to explicitly tell V8 to use it:
        v8::CompileUnbound(isolate, source, kConsumeParserCache);
      -----------------------------
      
      BUG=
      R=marja@chromium.org, yangguo@chromium.org
      
      Review URL: https://codereview.chromium.org/389573006
      
      git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22431 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      a42612b4
  28. 14 Jul, 2014 1 commit
  29. 08 Jul, 2014 2 commits
  30. 27 Jun, 2014 1 commit
  31. 13 Jun, 2014 1 commit
  32. 03 Jun, 2014 1 commit
  33. 27 May, 2014 1 commit
  34. 26 May, 2014 1 commit