1. 05 Nov, 2020 1 commit
    • Devlin Cronin's avatar
      Introduce Function::FunctionProtoToString() · 2ccd4dc5
      Devlin Cronin authored
      Add a new function on the public API to allow serializing a function to
      a string using the built-in toString() implementation, allowing
      serialization without worrying about untrusted author script overriding
      the toString() implementation. This is similar in nature to
      Object::ObjectProtoToString() (but that only returns "[object Function]"
      for any passed function).
      
      Add tests for the same.
      
      Bug: chromium:1144841
      Change-Id: Ie4c29b870034c0817c23bf91f9424f956098823d
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2514768Reviewed-by: 's avatarToon Verwaest <verwaest@chromium.org>
      Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#70976}
      2ccd4dc5
  2. 04 Nov, 2020 2 commits
  3. 02 Nov, 2020 1 commit
    • Ulan Degenbaev's avatar
      Fix alloc/dealloc size mismatch for v8::BackingStore · 9a49b229
      Ulan Degenbaev authored
      On newer compilers the {operator delete} with explicit {size_t}
      argument would be instantiated for {v8::BackingStore} and used
      in the destructor of {std::unique_ptr<v8::BackingStore>}. The {size_t}
      argument is wrong though, since the pointer actually points
      to a {v8::internal::BackingStore} object.
      The solution is to explicitly provide a {operator delete}, preventing
      an implicitly generated {size_t} operator.
      
      Bug:v8:11081
      
      Change-Id: Iee0aa47a67f0e41000bea628942f7e3d70198b83
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2506712
      Commit-Queue: Ulan Degenbaev <ulan@chromium.org>
      Reviewed-by: 's avatarCamillo Bruni <cbruni@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#70916}
      9a49b229
  4. 30 Oct, 2020 1 commit
    • Martin Bidlingmaier's avatar
      [regexp] Add 'l' flag to force experimental engine · 5720d205
      Martin Bidlingmaier authored
      This commit adds the 'l' (linear) RegExp flag (as in e.g. /asdf|123/l)
      that forces execution in linear time.  These regexps are handled by the
      experimental engine.  If the experimental engine cannot handle the
      pattern, an exception is thrown on creation of the regexp.
      
      The commit also adds a new global V8 flag and changes an existing one:
      * --enable-experimental-engine, which turns on recognition of the RegExp
        'l' flag.  Previously this flag also caused all supported regexps to
        be executed by the experimental engine; this is not the case anymore.
      * --default-to-experimental-regexp-engine takes over the previous
        semantics of --enable-experimental-regexp-engine:  We execute all
        supported regexps with the experimental engine.
      
      Cq-Include-Trybots: luci.v8.try:v8_linux64_fyi_rel_ng
      Bug: v8:10765
      Change-Id: I5622a89b19404105e8be280d454e9fdd63c003b3
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2461244Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
      Reviewed-by: 's avatarGeorg Neis <neis@chromium.org>
      Reviewed-by: 's avatarSimon Zünd <szuend@chromium.org>
      Reviewed-by: 's avatarJakob Gruber <jgruber@chromium.org>
      Commit-Queue: Martin Bidlingmaier <mbid@google.com>
      Cr-Commit-Position: refs/heads/master@{#70892}
      5720d205
  5. 29 Oct, 2020 1 commit
  6. 28 Oct, 2020 1 commit
  7. 27 Oct, 2020 3 commits
  8. 23 Oct, 2020 1 commit
  9. 20 Oct, 2020 1 commit
  10. 14 Oct, 2020 1 commit
  11. 13 Oct, 2020 1 commit
  12. 09 Oct, 2020 1 commit
  13. 07 Oct, 2020 1 commit
  14. 06 Oct, 2020 3 commits
  15. 29 Sep, 2020 1 commit
  16. 02 Sep, 2020 2 commits
  17. 01 Sep, 2020 2 commits
  18. 24 Aug, 2020 1 commit
  19. 17 Aug, 2020 1 commit
  20. 12 Aug, 2020 1 commit
  21. 10 Aug, 2020 2 commits
  22. 06 Aug, 2020 1 commit
  23. 03 Aug, 2020 1 commit
  24. 01 Aug, 2020 1 commit
    • Ulan Degenbaev's avatar
      [ukm] Rename v8::Context::Token to v8::metrics::Recorder::ContextId · 260ec995
      Ulan Degenbaev authored
      Chrome is currently adding a 128-bit V8ContextToken to keep track of
      V8 contexts across multiple isolates and processes. Having per-isolate
      token exposed by V8 leads to confusion of these two tokens.
      
      This moves v8::Context::Token to v8::metrics::Recorder and changes
      the corresponding functions:
      - v8::Context::GetToken => v8::metrics::Recorder::GetContextId
      - v8::Context::GetByToken => v8::metrics::Recorder::GetContext
      
      This CL is purely mechanical and does not change the behaviour.
      
      Bug: chromium:1101749
      Tbr: clemensb@chromium.org
      Change-Id: I31bbfa02ebab1c0d91b00f0d08c1b236392d14d2
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2330023
      Commit-Queue: Ulan Degenbaev <ulan@chromium.org>
      Reviewed-by: 's avatarEmanuel Ziegler <ecmziegler@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#69188}
      260ec995
  25. 31 Jul, 2020 1 commit
  26. 30 Jul, 2020 1 commit
  27. 29 Jul, 2020 1 commit
  28. 28 Jul, 2020 1 commit
  29. 24 Jul, 2020 1 commit
  30. 22 Jul, 2020 1 commit
  31. 17 Jul, 2020 1 commit
  32. 09 Jul, 2020 1 commit