1. 28 Aug, 2016 1 commit
  2. 25 Aug, 2016 1 commit
  3. 12 Aug, 2016 2 commits
  4. 10 Aug, 2016 2 commits
    • mlippautz's avatar
      Revert of [heap] Switch to 500k pages (patchset #24 id:780001 of... · 555c9619
      mlippautz authored
      Revert of [heap] Switch to 500k pages (patchset #24 id:780001 of https://codereview.chromium.org/2013713003/ )
      
      Reason for revert:
      Failures on waterfall:
      
      e.g. http://build.chromium.org/p/client.v8/builders/V8%20Linux64%20TSAN/builds/11134
      
      Original issue's description:
      > [heap] Switch to 500k pages
      >
      > - Decrease regular heap object size to 300k, keeping the same ration (60%)
      >   between this limit and page size.
      >
      > In a follow up, we can now get rid of the new space border page while
      > keeping the 1M minimum new space size.
      >
      > Some results (v8.infinite_scroll; 3 runs):
      > - evacuate.avg: +15.3% (1.4->1.2)
      > - evacuate.max: +24.4% (2.4->1.8)
      >
      > BUG=chromium:581412
      > LOG=N
      > R=hpayer@chromium.org, ulan@chromium.org, yangguo@chromium.org
      >
      > Committed: https://crrev.com/ffe5c670e1559d11e7b252e15fec38765e7dbe4f
      > Cr-Commit-Position: refs/heads/master@{#38533}
      
      TBR=hpayer@chromium.org,ulan@chromium.org,yangguo@chromium.org
      # Skipping CQ checks because original CL landed less than 1 days ago.
      NOPRESUBMIT=true
      NOTREECHECKS=true
      NOTRY=true
      BUG=chromium:581412
      
      Review-Url: https://codereview.chromium.org/2229403003
      Cr-Commit-Position: refs/heads/master@{#38537}
      555c9619
    • mlippautz's avatar
      [heap] Switch to 500k pages · ffe5c670
      mlippautz authored
      - Decrease regular heap object size to 300k, keeping the same ration (60%)
        between this limit and page size.
      
      In a follow up, we can now get rid of the new space border page while
      keeping the 1M minimum new space size.
      
      Some results (v8.infinite_scroll; 3 runs):
      - evacuate.avg: +15.3% (1.4->1.2)
      - evacuate.max: +24.4% (2.4->1.8)
      
      BUG=chromium:581412
      LOG=N
      R=hpayer@chromium.org, ulan@chromium.org, yangguo@chromium.org
      
      Review-Url: https://codereview.chromium.org/2013713003
      Cr-Commit-Position: refs/heads/master@{#38533}
      ffe5c670
  5. 28 Jun, 2016 1 commit
    • yangguo's avatar
      [snapshot] revisit snapshot API. · 872c461b
      yangguo authored
      This part of the snapshot API should not be in use yet, so we can still
      change this. The motivation for this change is:
      - Use MaybeHandle where reasonable.
      - Remove ambiguity: when we use index to create context from snapshot,
        we should not have a silent fallback if snapshot is not available.
      - Symmetry: rename to Context::FromSnapshot to mirror templates.
      
      R=jochen@chromium.org
      BUG=chromium:617892
      
      Review-Url: https://codereview.chromium.org/2100073002
      Cr-Commit-Position: refs/heads/master@{#37334}
      872c461b
  6. 15 Jun, 2016 1 commit
  7. 10 Jun, 2016 1 commit
  8. 08 Jun, 2016 1 commit
  9. 01 Mar, 2016 1 commit
  10. 01 Dec, 2015 1 commit
    • yangguo's avatar
      [bootstrapper] no longer use outdated contexts list. · 564a2086
      yangguo authored
      We currently use the outdated contexts list provided by the serializer
      to update the receiver (the global proxy) in script contexts. However,
      this is not actually necessary, since the global proxy is passed to the
      deserializer and replaced as we deserialize.
      
      Originally, the outdated contexts list is to update the global object
      field in contexts. This was necessary since at the time the deserializer
      creates the native context, the global object has not yet been created.
      But the global proxy already exists.
      
      R=bmeurer@chromium.org
      
      Review URL: https://codereview.chromium.org/1488873004
      
      Cr-Commit-Position: refs/heads/master@{#32483}
      564a2086
  11. 30 Sep, 2015 1 commit
  12. 20 Aug, 2015 2 commits
  13. 12 Jun, 2015 1 commit
  14. 20 Apr, 2015 1 commit
  15. 27 Mar, 2015 1 commit
  16. 25 Feb, 2015 1 commit
  17. 20 Feb, 2015 1 commit
  18. 14 Jan, 2015 2 commits
  19. 13 Jan, 2015 1 commit
  20. 10 Dec, 2014 2 commits
  21. 09 Dec, 2014 2 commits
  22. 05 Dec, 2014 1 commit
  23. 04 Dec, 2014 2 commits
  24. 21 Nov, 2014 1 commit
  25. 25 Sep, 2014 1 commit
  26. 19 Sep, 2014 1 commit
  27. 18 Sep, 2014 2 commits
  28. 23 Jun, 2014 1 commit
  29. 10 Jun, 2014 1 commit
  30. 05 Jun, 2014 1 commit
    • vogelheim@chromium.org's avatar
      Support external startup data in V8. · ba9f391b
      vogelheim@chromium.org authored
      [Retry of crrev.com/293993021, which caused problems with 'ninja all' in Chromium. First patch set if a clean apply
      of crrev.com/293993021. Subsequent sets are the actual fix
      for that issue.]
      
      If the embedder chooses, the 'natives' (library sources) and the
      precompiled startup blob can be written to files during the build
      process and handed over to V8 at startup. The main purpose would be
      to reduce the size of the compiled binary for space constrained
      platforms.
      
      The build-time option is off by default. Nothing should change if
      it's not enabled.
      
      BUG=
      R=jochen@chromium.org
      
      Review URL: https://codereview.chromium.org/315033002
      
      git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21696 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      ba9f391b
  31. 04 Jun, 2014 1 commit
  32. 03 Jun, 2014 1 commit