1. 18 May, 2017 1 commit
  2. 27 Apr, 2017 1 commit
  3. 07 Feb, 2017 1 commit
  4. 07 Sep, 2016 1 commit
  5. 01 Sep, 2016 1 commit
  6. 09 Dec, 2015 1 commit
  7. 16 Nov, 2015 1 commit
  8. 16 Sep, 2015 1 commit
  9. 31 Aug, 2015 2 commits
    • hablich's avatar
      Revert of [heap] More flag cleanup. (patchset #8 id:140001 of... · 6eb83769
      hablich authored
      Revert of [heap] More flag cleanup. (patchset #8 id:140001 of https://codereview.chromium.org/1314863003/ )
      
      Reason for revert:
      Breaks http://build.chromium.org/p/client.v8/builders/V8%20Arm%20-%20debug%20-%202/builds/2372
      
      Original issue's description:
      > [heap] GC flag cleanup/restructuring.
      >
      > * GC's flags are now proper flags and not int.
      > * Callback flags are not threaded through but only set once like gc flags
      > * Callers of methods that trigger GCs need to pass a reason when not using
      >   the default parameters.
      >
      > Furthermore, each GC invocation can be passed the GC and GCCallback flags. We
      > usually override the currently set flags upon finishing a GC cylce, but are able
      > to restore the previously set if desired. This is useful for explicitely
      > triggered scavenges or external requests that interrupt the current behaviour.
      >
      > BUG=
      >
      > Committed: https://crrev.com/f4f3b431b9ce0778d926acf03c0d36dae5c0cba4
      > Cr-Commit-Position: refs/heads/master@{#30457}
      
      TBR=hpayer@chromium.org,yangguo@chromium.org,mlippautz@chromium.org
      NOPRESUBMIT=true
      NOTREECHECKS=true
      NOTRY=true
      BUG=
      
      Review URL: https://codereview.chromium.org/1303393004
      
      Cr-Commit-Position: refs/heads/master@{#30463}
      6eb83769
    • mlippautz's avatar
      [heap] GC flag cleanup/restructuring. · f4f3b431
      mlippautz authored
      * GC's flags are now proper flags and not int.
      * Callback flags are not threaded through but only set once like gc flags
      * Callers of methods that trigger GCs need to pass a reason when not using
        the default parameters.
      
      Furthermore, each GC invocation can be passed the GC and GCCallback flags. We
      usually override the currently set flags upon finishing a GC cylce, but are able
      to restore the previously set if desired. This is useful for explicitely
      triggered scavenges or external requests that interrupt the current behaviour.
      
      BUG=
      
      Review URL: https://codereview.chromium.org/1314863003
      
      Cr-Commit-Position: refs/heads/master@{#30457}
      f4f3b431
  10. 17 Jul, 2015 1 commit
  11. 23 Apr, 2015 1 commit
  12. 15 Apr, 2015 2 commits
  13. 14 Apr, 2015 1 commit
  14. 13 Jun, 2014 1 commit
  15. 03 Jun, 2014 1 commit
  16. 23 May, 2014 1 commit
  17. 22 May, 2014 4 commits
  18. 03 Apr, 2014 1 commit
  19. 19 Mar, 2014 1 commit
    • mvstanton@chromium.org's avatar
      Pretenure call new support. · 535f3427
      mvstanton@chromium.org authored
      When FLAG_pretenure_call_new is on, we emit mementos on new object creation
      in full code, and consume the feedback in crankshaft. A key difference in the
      generated code for stubs is the allocation of an additional type vector slot for the
      CallNew AST node, which simplifies the CallConstructStub and CallFunctionStub
      considerably.
      
      Some performance tuning still needs to be addressed, therefore the flag is off at
      this moment, though fully functional. The goal is to remove the flag as soon as
      possible, which allows much code deletion (yay).
      
      R=hpayer@chromium.org
      
      Review URL: https://codereview.chromium.org/132963012
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@20076 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      535f3427
  20. 18 Feb, 2014 1 commit
  21. 04 Feb, 2014 1 commit
  22. 21 Jan, 2014 1 commit
  23. 14 Oct, 2013 1 commit
  24. 19 Sep, 2013 1 commit
  25. 26 Jun, 2013 2 commits
  26. 20 Jun, 2012 1 commit
  27. 08 Feb, 2012 1 commit
  28. 24 Jul, 2011 1 commit
  29. 15 Jul, 2011 1 commit
  30. 23 May, 2011 1 commit
  31. 18 Mar, 2011 3 commits
  32. 03 Sep, 2010 1 commit