1. 03 Mar, 2017 1 commit
  2. 10 Feb, 2017 1 commit
  3. 19 Jan, 2017 1 commit
  4. 13 Jan, 2017 1 commit
  5. 12 Jan, 2017 1 commit
  6. 09 Jan, 2017 1 commit
  7. 21 Dec, 2016 1 commit
  8. 16 Feb, 2016 1 commit
  9. 01 Jun, 2015 1 commit
  10. 18 Feb, 2015 2 commits
  11. 16 Feb, 2015 1 commit
    • ishell's avatar
      Property reconfiguring implemented. · 35841b50
      ishell authored
      Previous approach for property reconfiguration was to create a free-floating map with generalized representations of all fields. This patch does it right.
      
      When property is reconfigured either by changing its kind (kData <-> kAccessor) or its attributes it implies creation of a new branch in transition tree. If such a branch already existed before reconfiguration then it should be merged with the old (or source) branch of the transition tree. Merging procedure includes all the heavy machinery such as property location changes (kDescriptor -> kField), field representation/field type generalization, map deprecation, etc.
      
      Review URL: https://codereview.chromium.org/888623002
      
      Cr-Commit-Position: refs/heads/master@{#26667}
      35841b50
  12. 19 Jan, 2015 1 commit
    • ishell's avatar
      Massive renaming of PropertyType values and other implied stuff. · 33994b4a
      ishell authored
      PropertyKind:
        DATA -> kData
        ACCESSOR -> kAccessor
      
      PropertyType:
        FIELD -> DATA
        CONSTANT -> DATA_CONSTANT
        ACCESSOR_FIELD -> ACCESSOR
        CALLBACKS -> ACCESSOR_CONSTANT
      
      PropertyLocation:
        IN_OBJECT -> kField
        IN_DESCRIPTOR -> kDescriptor
      
      StoreMode:
        FORCE_IN_OBJECT -> FORCE_FIELD
      
      FieldDescriptor -> DataDescriptor
      ConstantDescriptor -> DataConstantDescriptor
      CallbacksDescriptor -> AccessorConstantDescriptor
      
      Review URL: https://codereview.chromium.org/856503002
      
      Cr-Commit-Position: refs/heads/master@{#26146}
      33994b4a
  13. 16 Dec, 2014 1 commit
  14. 12 Dec, 2014 1 commit
  15. 24 Nov, 2014 1 commit
  16. 19 Nov, 2014 1 commit
  17. 23 Oct, 2014 1 commit
  18. 30 Sep, 2014 1 commit
  19. 08 Sep, 2014 1 commit
  20. 26 Aug, 2014 1 commit
  21. 21 Aug, 2014 1 commit
  22. 20 Aug, 2014 1 commit
  23. 30 Jul, 2014 1 commit
  24. 07 Jul, 2014 1 commit
  25. 03 Jul, 2014 1 commit
  26. 10 Jun, 2014 2 commits
  27. 06 Jun, 2014 1 commit
  28. 03 Jun, 2014 1 commit
  29. 15 Apr, 2014 1 commit
  30. 14 Apr, 2014 2 commits
  31. 04 Apr, 2014 1 commit
  32. 01 Apr, 2014 1 commit
  33. 18 Feb, 2014 1 commit
  34. 24 Jul, 2013 1 commit
  35. 07 May, 2013 1 commit
  36. 13 Nov, 2012 1 commit
  37. 27 Aug, 2012 1 commit
    • verwaest@chromium.org's avatar
      Make order of addition the primary order of descriptor arrays. · efb53e14
      verwaest@chromium.org authored
      The order by name is maintained as secondary order by using unused bits in the property details.
      
      This is preliminary work towards sharing descriptors arrays.
      
      The change allows us
      - to get rid of the LastAdded bits in the map, binding it to the number of valid descriptors for the given map
      - to avoid resorting by enumeration index to create the cache
      - (maybe in the future, depending on performance) to get rid of the enumeration cache altogether.
      
      Although generally the number_of_descriptors equals the NumberOfOwnDescriptors in the current version, this is preliminary work towards sharing    descriptors, where maps may have more descriptors than are valid for the map.
      
      Review URL: https://chromiumcodereview.appspot.com/10879013
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@12385 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      efb53e14