1. 27 Nov, 2018 1 commit
  2. 14 Nov, 2018 1 commit
  3. 21 Jun, 2018 1 commit
  4. 17 Apr, 2018 1 commit
  5. 26 Jan, 2018 1 commit
  6. 09 Jan, 2018 1 commit
  7. 20 Oct, 2017 1 commit
  8. 19 Oct, 2017 2 commits
  9. 13 Oct, 2017 1 commit
  10. 29 Sep, 2017 1 commit
  11. 26 Sep, 2017 1 commit
  12. 20 Jul, 2017 1 commit
  13. 27 Jan, 2017 1 commit
  14. 16 Jan, 2017 1 commit
  15. 19 Dec, 2016 1 commit
  16. 08 Aug, 2016 1 commit
  17. 21 Jul, 2016 1 commit
    • rmcilroy's avatar
      [Interpreter] Avoid accessing on-heap literal in VisitLiteral. · 6b5949a8
      rmcilroy authored
      Move VisitLiteral to decide what type of literal is being emitted by
      checking the raw ASTValue type, instead of the internalized on-heap
      value. This is required for concurrent bytecode generation.
      
      As part of this change, the NUMBER AstValue constructor is modified to
      try to convert numbers without a dot to SMIs where possible. This is to
      maintain the behavior in NewNumber where such numbers are internalized as
      SMIs, and ensures that we still emit LdaSmi bytecodes for these values
      in the generated bytecode.
      
      BUG=v8:5203
      
      Review-Url: https://codereview.chromium.org/2152853002
      Cr-Commit-Position: refs/heads/master@{#37931}
      6b5949a8
  18. 29 Jun, 2016 1 commit
  19. 06 Feb, 2016 1 commit
    • ishell's avatar
      [api] Make ObjectTemplate::SetNativeDataProperty() work even if the... · da213b6e
      ishell authored
      [api] Make ObjectTemplate::SetNativeDataProperty() work even if the ObjectTemplate does not have a constructor.
      
      Previously ObjectTemplate::New() logic relied on the fact that all the accessor properties are already installed in the initial map of the function object of the constructor FunctionTemplate.
      When the FunctionTemplate were instantiated the accessors of the instance templates from the whole inheritance chain were accumulated and added to the initial map.
      ObjectTemplate::SetSetAccessor() used to explicitly ensure that the ObjectTemplate has a constructor and therefore an initial map to add all accessors to.
      
      The new approach is to add all the accessors and data properties to the object exactly when the ObjectTemplate is instantiated. In order to keep it fast we now cache the object boilerplates in the Isolate::template_instantiations_cache (the former function_cache), so the object creation turns to be a deep copying of the boilerplate object.
      
      BUG=chromium:579009
      LOG=Y
      
      Committed: https://crrev.com/6a118774244d087b5979e9291d628a994f21d59d
      Cr-Commit-Position: refs/heads/master@{#33674}
      
      Review URL: https://codereview.chromium.org/1642223003
      
      Cr-Commit-Position: refs/heads/master@{#33798}
      da213b6e
  20. 03 Feb, 2016 1 commit
    • hablich's avatar
      Revert of [api] Make ObjectTemplate::SetNativeDataProperty() work even if the... · db47a31f
      hablich authored
      Revert of [api] Make ObjectTemplate::SetNativeDataProperty() work even if the ObjectTemplate does not have a … (patchset #3 id:80001 of https://codereview.chromium.org/1642223003/ )
      
      Reason for revert:
      Fails a lot of layout tests and blocks the roll. Can be easily reproduced with a local Chromium checkout.
      
      Reference: https://codereview.chromium.org/1652413003/
      
      Original issue's description:
      > [api] Make ObjectTemplate::SetNativeDataProperty() work even if the ObjectTemplate does not have a constructor.
      >
      > Previously ObjectTemplate::New() logic relied on the fact that all the accessor properties are already installed in the initial map of the function object of the constructor FunctionTemplate.
      > When the FunctionTemplate were instantiated the accessors of the instance templates from the whole inheritance chain were accumulated and added to the initial map.
      > ObjectTemplate::SetSetAccessor() used to explicitly ensure that the ObjectTemplate has a constructor and therefore an initial map to add all accessors to.
      >
      > The new approach is to add all the accessors and data properties to the object exactly when the ObjectTemplate is instantiated. In order to keep it fast we now cache the object boilerplates in the Isolate::template_instantiations_cache (the former function_cache), so the object creation turns to be a deep copying of the boilerplate object.
      >
      > This CL also prohibits non-primitive properties in ObjectTemplate to avoid potential cross-context leaks.
      >
      > BUG=chromium:579009
      > LOG=Y
      >
      > Committed: https://crrev.com/6a118774244d087b5979e9291d628a994f21d59d
      > Cr-Commit-Position: refs/heads/master@{#33674}
      
      TBR=verwaest@chromium.org,ishell@chromium.org
      # Skipping CQ checks because original CL landed less than 1 days ago.
      NOPRESUBMIT=true
      NOTREECHECKS=true
      NOTRY=true
      BUG=chromium:579009
      
      Review URL: https://codereview.chromium.org/1660263003
      
      Cr-Commit-Position: refs/heads/master@{#33698}
      db47a31f
  21. 02 Feb, 2016 1 commit
    • ishell's avatar
      [api] Make ObjectTemplate::SetNativeDataProperty() work even if the... · 6a118774
      ishell authored
      [api] Make ObjectTemplate::SetNativeDataProperty() work even if the ObjectTemplate does not have a constructor.
      
      Previously ObjectTemplate::New() logic relied on the fact that all the accessor properties are already installed in the initial map of the function object of the constructor FunctionTemplate.
      When the FunctionTemplate were instantiated the accessors of the instance templates from the whole inheritance chain were accumulated and added to the initial map.
      ObjectTemplate::SetSetAccessor() used to explicitly ensure that the ObjectTemplate has a constructor and therefore an initial map to add all accessors to.
      
      The new approach is to add all the accessors and data properties to the object exactly when the ObjectTemplate is instantiated. In order to keep it fast we now cache the object boilerplates in the Isolate::template_instantiations_cache (the former function_cache), so the object creation turns to be a deep copying of the boilerplate object.
      
      This CL also prohibits non-primitive properties in ObjectTemplate to avoid potential cross-context leaks.
      
      BUG=chromium:579009
      LOG=Y
      
      Review URL: https://codereview.chromium.org/1642223003
      
      Cr-Commit-Position: refs/heads/master@{#33674}
      6a118774
  22. 13 Aug, 2015 2 commits
  23. 30 Mar, 2015 1 commit
  24. 10 Mar, 2015 1 commit
  25. 22 Oct, 2014 1 commit
  26. 22 Sep, 2014 1 commit
  27. 12 Sep, 2014 1 commit
  28. 04 Aug, 2014 1 commit
  29. 30 Jun, 2014 1 commit
  30. 20 Jun, 2014 1 commit
  31. 03 Jun, 2014 1 commit
  32. 26 May, 2014 1 commit
  33. 29 Apr, 2014 1 commit
  34. 28 Apr, 2014 1 commit
  35. 11 Apr, 2014 1 commit
  36. 20 Dec, 2013 1 commit
  37. 19 Jul, 2013 1 commit
  38. 30 Jul, 2012 1 commit