1. 28 Mar, 2011 1 commit
  2. 22 Dec, 2010 1 commit
  3. 15 Dec, 2010 1 commit
  4. 07 Dec, 2010 3 commits
  5. 15 Nov, 2010 1 commit
  6. 04 Nov, 2010 1 commit
  7. 26 Oct, 2010 2 commits
  8. 25 Oct, 2010 2 commits
  9. 24 Sep, 2010 1 commit
    • dimich@chromium.org's avatar
      Add CODE_POINTER_ALIGN, use it in Page to align generated code. · 589eb4a8
      dimich@chromium.org authored
      The object's space in Page starts after Page header and is aligned to kMapAlignment which is 32 bytes on 32-bit and 8 bytes on 64-bit.
      
      In case of 64-bit target, the current page header size is exactly 32 bytes so we get the code magically aligned at 32 bytes but it is better to have a separate CODE_POINTER_ALIGN macro to make sure the object space in Page is aligned properly for both maps and code.
      
      There could be a small waste of bytes sometimes (since both Page header and Code header sizes are aligned separately) but it seems the optimal one would involve cross-dependencies between .h files and not clear if it's worth it.
      
      This is a back-port from Isolates branch.
      
      Review URL: http://codereview.chromium.org/3461021
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@5526 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      589eb4a8
  10. 31 Aug, 2010 1 commit
  11. 27 Aug, 2010 1 commit
  12. 16 Aug, 2010 1 commit
  13. 05 Aug, 2010 1 commit
  14. 14 Jul, 2010 1 commit
  15. 13 Jul, 2010 1 commit
  16. 02 Jul, 2010 1 commit
  17. 04 Jun, 2010 1 commit
  18. 27 May, 2010 1 commit
  19. 26 May, 2010 1 commit
  20. 25 May, 2010 1 commit
    • vegorov@chromium.org's avatar
      Cardmarking writebarrier. · 675e711f
      vegorov@chromium.org authored
      - New сardmarking write barrier handles large objects and normal objects in a similar fashion (no more additional space for pointer tracking is required, no conditional branches in WB code).
      - Changes to enable oldspaces iteration without maps decoding:
      -- layout change for FixedArrays: length is stored as a smis (initial patch by
      Kevin Millikin)
      -- layout change for SharedFunctionInfo: integer fields are stored as smi on
      arm, ia32 and rearranged on x64.
      -- layout change for String: meaning of LSB bit is fliped (1 now means hash not
      computed); on x64 padding is added.
      -- layout of maps is _not_ changed. Map space is currently iterated in a special
      way.
      
      Review URL: http://codereview.chromium.org/2144006
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@4715 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      675e711f
  21. 21 May, 2010 2 commits
  22. 20 May, 2010 2 commits
  23. 17 May, 2010 1 commit
    • mark@chromium.org's avatar
      Allow build-time selection between ia32 and x86_64 in the GYP/Xcode Mac · e9b5d785
      mark@chromium.org authored
      Chromium build.
      
      v8.gyp no longer sets any V8_TARGET_ARCH_* macro on the Mac. Instead, the
      proper V8_TARGET_ARCH_* macro will be set by src/globals.h in the same way as
      the V8_HOST_ARCH_* macro when it detects that no target macro is currently
      defined. The Mac build will attempt to compile all ia32 and x86_64 .cc files.
      #ifdef guards in each of these target-specific source files prevent their
      compilation when the associated target is not selected. For completeness,
      these #ifdef guards are also provided for the arm and mips .cc files.
      
      BUG=706
      TEST=x86_64 Mac GYP/Xcode-based Chromium build (still depends on other changes)
      Review URL: http://codereview.chromium.org/2133003
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@4666 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      e9b5d785
  24. 06 May, 2010 1 commit
  25. 26 Apr, 2010 1 commit
  26. 20 Apr, 2010 3 commits
  27. 15 Apr, 2010 1 commit
    • ager@chromium.org's avatar
      Reapply load ICs for nonexistent properties. · afc15bb4
      ager@chromium.org authored
      We need to be careful to check global property cells for the property
      encountered during lookup.  Therefore, the ICs have to be specific to
      the name of the property if global objects are involved.  In
      principle, this means that we could get a large number of monomorphic
      ICs for the same map if there is a global object in the prototype
      chain.  However, since this is only done for normal load ICs and not
      for keyed load ICs I do not expect this to be a problem.  I will
      experiment with it once this goes in.
      
      BUG=675
      Review URL: http://codereview.chromium.org/1559033
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@4426 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      afc15bb4
  28. 14 Apr, 2010 2 commits
  29. 12 Apr, 2010 1 commit
  30. 07 Apr, 2010 1 commit
  31. 06 Apr, 2010 1 commit