Skip to content

V
V8
Switch branch/tag
  1. 29 Jan, 2010 1 commit
  3. 01 Dec, 2009 1 commit
  5. 04 Nov, 2009 2 commits
  7. 29 Oct, 2009 1 commit
  9. 27 Oct, 2009 1 commit
  11. 26 Oct, 2009 2 commits
  13. 15 Sep, 2009 1 commit
  15. 26 Aug, 2009 1 commit
  17. 14 Aug, 2009 1 commit
  19. 30 Jul, 2009 1 commit
    • sgjesse@chromium.org's avatar
      Avoid dictionary expansion during bootstrapping. · cffc0511
      sgjesse@chromium.org authored 
      Allocate the code stubs dictionary and non monomorphic cache dictionary with an initial size which avoids these dictionaries to be expanded during bootstrapping. This gets rid of 9 dictionary expansions during bootstrapping.

Preallocate the dictionary when normalizing an object to a size sufficient for holding the number of properties which is expected to be added to the object. This is used when ceating an object from an object literal boilerplate where multiple properties are known to be added.  This gets rid of 10 dictionary expansions during bootstrapping.

There are now 3 dictionary expansions left during bootstrapping.
Review URL: http://codereview.chromium.org/160382

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@2584 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      cffc0511
  21. 07 Jul, 2009 1 commit
  23. 08 Jun, 2009 2 commits
  25. 25 May, 2009 1 commit
  27. 12 May, 2009 1 commit
  29. 24 Apr, 2009 1 commit
  31. 21 Apr, 2009 1 commit
  33. 19 Mar, 2009 1 commit
  35. 18 Mar, 2009 1 commit
  37. 10 Mar, 2009 1 commit
  39. 03 Feb, 2009 1 commit
  41. 23 Jan, 2009 2 commits
  43. 15 Jan, 2009 1 commit
  45. 12 Jan, 2009 1 commit
  47. 17 Nov, 2008 1 commit
  49. 22 Oct, 2008 1 commit
  51. 21 Oct, 2008 1 commit
    • feng@chromium.org's avatar
      Split window support from V8. · 42ef2c3d
      feng@chromium.org authored 
      Here is a description of the background and design of split window in Chrome and V8:
https://docs.google.com/a/google.com/Doc?id=chhjkpg_47fwddxbfr

This change list splits the window object into two parts: 1) an inner window object used as the global object of contexts; 2) an outer window object exposed to JavaScript and accessible by the name 'window'. Firefox did it awhile ago, here are some discussions: https://wiki.mozilla.org/Gecko:SplitWindow. One additional benefit of splitting window in Chrome is that accessing global variables don't need security checks anymore, it can improve applications that use many global variables.

V8 support of split window:
  There are a small number of changes on V8 api to support split window:
Security context is removed from V8, so does related API functions;
A global object can be detached from its context and reused by a new context;
Access checks on an object template can be turned on/off by default;
An object can turn on its access checks later;

  V8 has a new object type, ApiGlobalObject, which is the outer window object type. The existing JSGlobalObject becomes the inner window object type. Security checks are moved from JSGlobalObject to ApiGlobalObject. ApiGlobalObject is the one exposed to JavaScript, it is accessible through Context::Global(). ApiGlobalObject's prototype is set to JSGlobalObject so that property lookups are forwarded to JSGlobalObject. ApiGlobalObject forwards all other property access requests to JSGlobalObject, such as SetProperty, DeleteProperty, etc.

  Security token is moved to a global context, and ApiGlobalObject has a reference to its global context. JSGlobalObject has a reference to its global context as well. When accessing properties on a global object in JavaScript, the domain security check is performed by comparing the security token of the lexical context (Top::global_context()) to the token of global object's context. The check is only needed when the receiver is a window object, such as 'window.document'. Accessing global variables, such as 'var foo = 3; foo' does not need checks because the receiver is the inner window object.

  When an outer window is detached from its global context (when a frame navigates away from a page), it is completely detached from the inner window. A new context is created for the new page, and the outer global object is reused. At this point, the access check on the DOMWindow wrapper of the old context is turned on. The code in old context is still able to access DOMWindow properties, but it has to go through domain security checks.


It is debatable on how to implement the outer window object. Currently each property access function has to check if the receiver is ApiGlobalObject type. This approach might be error-prone that one may forget to check the receiver when adding new functions. It is unlikely a performance issue because accessing global variables are more common than 'window.foo' style coding.

I am still working on the ARM port, and I'd like to hear comments and suggestions on the best way to support it in V8.


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

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@540 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      42ef2c3d
  53. 02 Oct, 2008 1 commit
  55. 09 Sep, 2008 1 commit
  57. 29 Aug, 2008 1 commit
  59. 03 Jul, 2008 1 commit