1. 27 Dec, 2012 1 commit
  2. 24 Dec, 2012 1 commit
  3. 18 Dec, 2012 1 commit
  4. 13 Dec, 2012 2 commits
  5. 12 Dec, 2012 1 commit
  6. 10 Dec, 2012 1 commit
  7. 05 Dec, 2012 2 commits
  8. 04 Dec, 2012 1 commit
  9. 03 Dec, 2012 3 commits
  10. 30 Nov, 2012 2 commits
  11. 12 Nov, 2012 2 commits
  12. 08 Nov, 2012 1 commit
    • rossberg@chromium.org's avatar
      Delivery logic for Object.observe · c203f054
      rossberg@chromium.org authored
      This CL has two parts: the first is the logic itself, whereby each observer callback is assigned
      a "priority" number the first time it's passed as an observer to Object.observe(), and that
      priority is used to determine the order of delivery.
      
      The second part invokes the above logic as part of the API, when the JS stack winds down to
      zero.
      
      Added several tests via the API, as the delivery logic isn't testable from a JS test
      (it runs after such a test would exit).
      
      Review URL: https://codereview.chromium.org/11266011
      Patch from Adam Klein <adamk@chromium.org>.
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@12902 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      c203f054
  13. 14 Sep, 2012 1 commit
    • erik.corry@gmail.com's avatar
      Refactoring of snapshots. This simplifies and improves · 5a8d1764
      erik.corry@gmail.com authored
      the speed of deserializing code.  The current startup
      time improvement for V8 is around 6%, but code deserialization
      is speeded up disproportionately, and we will soon have more
      code in the snapshot.
      * Removed support for deserializing into large object space.
        The regular pages are 1Mbyte now and that is plenty.  This
        is a big simplification.
      * Instead of reserving space for the snapshot we actually
        allocate it now.  This removes some special casing from
        the memory management and simplifies deserialization since
        we are just bumping a pointer rather than calling the
        normal allocation routines during deserialization.
      * Record in the snapshot how much we need to boot up and
        allocate it instead of just assuming that allocations in
        a new VM will always be linear.
      * In the snapshot we always address an object as a negative
        offset from the current allocation point.  We used to
        sometimes address from the start of the deserialized data,
        but this is less useful now that we have good support for
        roots and repetitions in the deserialization data.
      * Code objects were previously deserialized (like other
        objects) by alternating raw data (deserialized with memcpy)
        and pointers (to external references, other objects, etc.).
        Now we deserialize code objects with a single memcpy,
        followed by a series of skips and pointers that partially
        overwrite the code we memcopied out of the snapshot.
        The skips are sometimes merged into the following
        instruction in the deserialization data to reduce dispatch
        time.
      * Integers in the snapshot were stored in a variable length
        format that gives a compact representation for small positive
        integers.  This is still the case, but the new encoding can
        be decoded without branches or conditional instructions,
        which is faster on a modern CPU.
      Review URL: https://chromiumcodereview.appspot.com/10918067
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@12505 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      5a8d1764
  14. 05 Sep, 2012 1 commit
  15. 28 Aug, 2012 2 commits
  16. 21 Aug, 2012 1 commit
  17. 17 Aug, 2012 2 commits
  18. 06 Aug, 2012 1 commit
  19. 19 Jul, 2012 1 commit
  20. 18 Jul, 2012 1 commit
  21. 12 Jul, 2012 1 commit
  22. 20 Jun, 2012 1 commit
  23. 19 Jun, 2012 1 commit
  24. 11 Jun, 2012 4 commits
  25. 04 Jun, 2012 1 commit
  26. 22 May, 2012 1 commit
  27. 23 Apr, 2012 1 commit
  28. 18 Apr, 2012 2 commits