1. 21 Mar, 2014 1 commit
  2. 12 Feb, 2014 1 commit
  3. 04 Feb, 2014 1 commit
  4. 20 Dec, 2013 1 commit
  5. 18 Dec, 2013 1 commit
  6. 15 Nov, 2013 1 commit
  7. 19 Jul, 2013 1 commit
  8. 23 May, 2013 1 commit
  9. 17 Jan, 2013 1 commit
  10. 05 Dec, 2012 1 commit
  11. 26 Nov, 2012 1 commit
  12. 23 May, 2012 1 commit
  13. 12 Mar, 2012 1 commit
  14. 05 Mar, 2012 1 commit
  15. 02 Mar, 2012 2 commits
  16. 24 Nov, 2011 1 commit
  17. 17 Nov, 2011 1 commit
  18. 20 Oct, 2011 1 commit
  19. 07 Apr, 2011 1 commit
  20. 18 Mar, 2011 3 commits
  21. 07 Dec, 2010 3 commits
  22. 11 Nov, 2010 1 commit
  23. 18 Oct, 2010 1 commit
  24. 14 Sep, 2010 1 commit
  25. 01 Sep, 2010 1 commit
  26. 30 Aug, 2010 1 commit
  27. 27 Aug, 2010 2 commits
  28. 20 Aug, 2010 1 commit
  29. 16 Aug, 2010 2 commits
    • 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
    • sgjesse@chromium.org's avatar
      ARM: backend opt for ToBoolean: JIT code generation for ToBool · e61bd7bd
      sgjesse@chromium.org authored
      Upgraded the CodeGenerator::ToBoolean() function in the ARM backend to use complete JIT code generation and not make runtime calls to ToBool (when VFP is enabled). 
      
      This change also includes the vcmp VFP instruction that supports a constant 0.0 as the second operand. 
      
      Patch by Subrato K De <subratokde@codeaurora.org>
      
      
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@5267 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      e61bd7bd
  30. 12 Aug, 2010 1 commit
    • sgjesse@chromium.org's avatar
      Handle overwriting valueOf on String objects correctly when adding · 8e0cd6db
      sgjesse@chromium.org authored
      This adds a check to the fast case string add to ensure that the String object still have the default valueOf function. The default valueOf is sitting on a hidden prototype of String.prototype.
      
      Before using the fast case valueOf the object is checked for a local valueOf property. For slow case objects this check always reports true (the dictionary is not probed, so valueOf might be there) and for fast case objects the descriptor array is checked for the valueOf symbol (just liniar scan). After that the prototype is checked for beeing the initial value of String.prototype. If this all pass (that is the default valueOf is still in place) this result is cached on the map making the check fast the next time.
      
      This is only implemented in the optimizing compiler, as the two usages of %_IsStringWrapperSafeForDefaultValueOf is never hit by the full compiler.
      
      I will port to x64 and ARM when this has been reviewed for ia32.
      
      I will remove the performance counters prior to final commit.
      
      BUG=http://code.google.com/p/v8/issues/detail?id=760
      TEST=test/mjsunit/regress/regress-760-1.js
      TEST=test/mjsunit/regress/regress-760-2.js
      
      Review URL: http://codereview.chromium.org/3117006
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@5252 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      8e0cd6db
  31. 09 Aug, 2010 1 commit
  32. 06 Aug, 2010 1 commit
  33. 16 Jul, 2010 1 commit
    • ricow@chromium.org's avatar
      Refactor type checks in v8natives.js and runtime.js. · 49573265
      ricow@chromium.org authored
      This includes adding a new inline IsSpecObject method to the code
      generator.  The old approach was somehow ineffecient since we would
      call both IsObject, IsUndetectable and IsFunction to determine if
      something was an object according to the spec. This change introduces
      a new macro that determines if something is an object according to the
      spec (and this does not include null). 
      
      This change also corrects a few places where undetectable objects was
      not allowed even when they should be (priorly they would use only
      IS_SPEC_OBJECT_OR_NULL, which would return false on an undetectable
      object, the new IS_SPEC_OBJECT returns true on an undetectable object.
      
      Review URL: http://codereview.chromium.org/2877018
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@5087 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      49573265