Skip to content

V
V8
Switch branch/tag
  1. 23 May, 2011 1 commit
  3. 18 Mar, 2011 3 commits
  5. 07 Dec, 2010 3 commits
  7. 20 Aug, 2010 1 commit
  9. 16 Aug, 2010 1 commit
    • vitalyr@chromium.org's avatar
      Copy-on-write arrays. · 3202df6c
      vitalyr@chromium.org authored 
      Object model changes
----------------------------------------
New fixed_cow_array_map is used for the elements array of a JSObject
to mark it as COW. The JSObject's map and other fields are not
affected. The JSObject's map still has the "fast elements" bit set. It
means we can do only the receiver map check in keyed loads and the
receiver and the elements map checks in keyed stores. So introducing
COW arrays doesn't hurt performance of these operations. But note that
the elements map check is necessary in all mutating operations because
the "has fast elements" bit now means "has fast elements for reading".
EnsureWritableFastElements can be used in runtime functions to perform
the necessary lazy copying.

Generated code changes
----------------------------------------
Generic keyed load is updated to only do the receiver map check (this
could have been done earlier). FastCloneShallowArrayStub now has two
modes: clone elements and use COW elements. AssertFastElements macro
is added to check the elements when necessary. The custom call IC
generators for Array.prototype.{push,pop} are updated to avoid going
to the slow case (and patching the IC) when calling the builtin should
work.

COW enablement
----------------------------------------
Currently we only put shallow and simple literal arrays in the COW
mode. This is done by the parser.

Review URL: http://codereview.chromium.org/3144002

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@5275 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      3202df6c
  11. 11 Aug, 2010 2 commits
  13. 20 May, 2010 3 commits
  15. 14 Apr, 2010 1 commit
  17. 23 Mar, 2010 1 commit
  19. 27 Jan, 2010 1 commit
  21. 21 Jan, 2010 1 commit
  23. 18 Jan, 2010 1 commit
    • mikhail.naganov@gmail.com's avatar
      Fix issue 571: display descriptive names for code objects from snapshot. · 37d39724
      mikhail.naganov@gmail.com authored 
      As this is only needed for internal profiling (not for DevTools),
the following approach had been chosen:

 - during snapshot creation, positions of serialized objects inside
   a snapshot are logged;

 - then during V8 initialization, positions of deserealized objects
   are logged;

 - those positions are used for retrieving code objects names from
   snapshot creation log, which needs to be supplied to tick processor
   script.

Positions logging is controlled with the new flag: --log_snapshot_positions.
This flag is turned off by default, and this adds no startup penalty.

To plug this fix to Golem, the following actions are needed:

 - logs created using 'mksnapshot' need to be stored along with VM images;

 - tick processor script needs to be run with '--snapshot-log=...' cmdline
   argument.

BUG=571

Review URL: http://codereview.chromium.org/551062

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@3635 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      37d39724
  25. 15 Jan, 2010 1 commit
  27. 12 Jan, 2010 1 commit
  29. 16 Nov, 2009 1 commit
  31. 13 Nov, 2009 1 commit
  33. 11 Nov, 2009 1 commit
  35. 06 Nov, 2009 1 commit
  37. 03 Nov, 2009 1 commit
  39. 30 Oct, 2009 1 commit
  41. 27 Oct, 2009 1 commit
  43. 21 Sep, 2009 1 commit
  45. 18 Sep, 2009 1 commit
  47. 09 Sep, 2009 1 commit
  49. 09 Jul, 2009 1 commit
  51. 25 May, 2009 1 commit
  53. 07 May, 2009 1 commit
  55. 06 May, 2009 1 commit
  57. 25 Feb, 2009 1 commit
  59. 26 Jan, 2009 2 commits
  61. 16 Jan, 2009 2 commits