Skip to content

V
V8
Switch branch/tag
  1. 04 Jan, 2013 1 commit
  3. 03 Jan, 2013 2 commits
  5. 28 Dec, 2012 4 commits
  7. 21 Dec, 2012 3 commits
  9. 19 Dec, 2012 1 commit
  11. 18 Dec, 2012 2 commits
  13. 17 Dec, 2012 1 commit
  15. 10 Dec, 2012 2 commits
  17. 07 Dec, 2012 1 commit
  19. 05 Dec, 2012 3 commits
  21. 03 Dec, 2012 2 commits
  23. 30 Nov, 2012 2 commits
  25. 29 Nov, 2012 1 commit
  27. 28 Nov, 2012 1 commit
  29. 27 Nov, 2012 1 commit
  31. 26 Nov, 2012 2 commits
  33. 23 Nov, 2012 1 commit
  35. 22 Nov, 2012 4 commits
    • svenpanne@chromium.org's avatar
      Moved buffer handling to AssemblerBase. · 51f5a8e7
      svenpanne@chromium.org authored 
      This removed a lot of copy-n-paste code and is very handy for some upcoming
changes (regarding predictable code size).

Review URL: https://codereview.chromium.org/11416133

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@13034 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      51f5a8e7
    • rossberg@chromium.org's avatar
      Get rid of static module allocation, do it in code. · ce05280b
      rossberg@chromium.org authored 
      Modules now have their own local scope, represented by their own context.
Module instance objects have an accessor for every export that forwards
access to the respective slot from the module's context. (Exports that are
modules themselves, however, are simple data properties.)

All modules have a _hosting_ scope/context, which (currently) is the
(innermost) enclosing global scope. To deal with recursion, nested modules
are hosted by the same scope as global ones.

For every (global or nested) module literal, the hosting context has an
internal slot that points directly to the respective module context. This
enables quick access to (statically resolved) module members by 2-dimensional
access through the hosting context. For example,

  module A {
    let x;
    module B { let y; }
  }
  module C { let z; }

allocates contexts as follows:

[header| .A | .B | .C | A | C ]  (global)
          |    |    |
          |    |    +-- [header| z ]  (module)
          |    |
          |    +------- [header| y ]  (module)
          |
          +------------ [header| x | B ]  (module)

Here, .A, .B, .C are the internal slots pointing to the hosted module
contexts, whereas A, B, C hold the actual instance objects (note that every
module context also points to the respective instance object through its
extension slot in the header).

To deal with arbitrary recursion and aliases between modules,
they are created and initialized in several stages. Each stage applies to
all modules in the hosting global scope, including nested ones.

1. Allocate: for each module _literal_, allocate the module contexts and
   respective instance object and wire them up. This happens in the
   PushModuleContext runtime function, as generated by AllocateModules
   (invoked by VisitDeclarations in the hosting scope).

2. Bind: for each module _declaration_ (i.e. literals as well as aliases),
   assign the respective instance object to respective local variables. This
   happens in VisitModuleDeclaration, and uses the instance objects created
   in the previous stage.
   For each module _literal_, this phase also constructs a module descriptor
   for the next stage. This happens in VisitModuleLiteral.

3. Populate: invoke the DeclareModules runtime function to populate each
   _instance_ object with accessors for it exports. This is generated by
   DeclareModules (invoked by VisitDeclarations in the hosting scope again),
   and uses the descriptors generated in the previous stage.

4. Initialize: execute the module bodies (and other code) in sequence. This
   happens by the separate statements generated for module bodies. To reenter
   the module scopes properly, the parser inserted ModuleStatements.

R=mstarzinger@chromium.org,svenpanne@chromium.org
BUG=

Review URL: https://codereview.chromium.org/11093074

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@13033 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      ce05280b
    • mvstanton@chromium.org's avatar
      Add dehoisting to the string printout of hydrogen and lithium instructions. · 80819f61
      mvstanton@chromium.org authored 
      This is nice when looking at hydrogen graphs, to see the real key offset.

R=mmassi@chromium.org
BUG=

Review URL: https://codereview.chromium.org/11348176

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@13032 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      80819f61
    • hpayer@chromium.org's avatar
      Use slot instead of value in the write barrier to record write from code. · ee164ffe
      hpayer@chromium.org authored 
      BUG=

Review URL: https://codereview.chromium.org/11412096

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@13029 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      ee164ffe
  37. 21 Nov, 2012 3 commits
  39. 20 Nov, 2012 1 commit
  41. 16 Nov, 2012 1 commit
  43. 15 Nov, 2012 1 commit