1. 20 Oct, 2020 1 commit
  2. 14 Oct, 2020 1 commit
  3. 13 Oct, 2020 1 commit
  4. 09 Oct, 2020 1 commit
  5. 07 Oct, 2020 1 commit
  6. 06 Oct, 2020 3 commits
  7. 29 Sep, 2020 1 commit
  8. 02 Sep, 2020 2 commits
  9. 01 Sep, 2020 2 commits
  10. 24 Aug, 2020 1 commit
  11. 17 Aug, 2020 1 commit
  12. 12 Aug, 2020 1 commit
  13. 10 Aug, 2020 2 commits
  14. 06 Aug, 2020 1 commit
  15. 03 Aug, 2020 1 commit
  16. 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
  17. 31 Jul, 2020 1 commit
  18. 30 Jul, 2020 1 commit
  19. 29 Jul, 2020 1 commit
  20. 28 Jul, 2020 1 commit
  21. 24 Jul, 2020 1 commit
  22. 22 Jul, 2020 1 commit
  23. 17 Jul, 2020 1 commit
  24. 09 Jul, 2020 1 commit
  25. 07 Jul, 2020 1 commit
  26. 01 Jul, 2020 1 commit
  27. 23 Jun, 2020 1 commit
  28. 22 Jun, 2020 1 commit
  29. 19 Jun, 2020 1 commit
  30. 12 Jun, 2020 1 commit
    • Daniel Bevenius's avatar
      Suppress cast-function-type in PersistentBase::SetWeak · f08cbfdc
      Daniel Bevenius authored
      This issue was seen in Node.js when compiling with GCC. It can also
      been see if building V8 using GCC and enabling -Wcast-function-type
      in BUILD.gn:
        "-Wcast-function-type",
      
      There are unit tests in V8 that produce this warning, for example
      test/cctest/test-global-handles.cc (formatted to fit the commit
      message width):
      g++ -MMD -MF obj/test/cctest/cctest_sources/test-global-handles.o.d
      ...
      In file included from ../../include/v8-inspector.h:14,
                       from ../../src/execution/isolate.h:15,
                       from ../../src/api/api.h:10,
                       from ../../src/api/api-inl.h:8,
                       from ../../test/cctest/test-global-handles.cc:28:
      ../../include/v8.h:
      In instantiation of ‘void v8::PersistentBase<T>::SetWeak(
          P*,
          typename v8::WeakCallbackInfo<P>::Callback,
          v8::WeakCallbackType)
      [with
        P = v8::Global<v8::Object>;
        T = v8::Object;
        typename v8::WeakCallbackInfo<P>::Callback =
        void (*)(const v8::WeakCallbackInfo<v8::Global<v8::Object> >&)
      ]’:
      ../../test/cctest/test-global-handles.cc:292:47: required from here
      ../../include/v8.h:10750:16: warning:
      cast between incompatible function types from
      ‘v8::WeakCallbackInfo<v8::Global<v8::Object> >::Callback’ {aka
      ‘void (*)(const v8::WeakCallbackInfo<v8::Global<v8::Object> >&)’} to
      ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’}
      [-Wcast-function-type]
      10750 |                reinterpret_cast<Callback>(callback), type);
            |                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      
      This commit suggests adding a pragma specifically for GCC to suppress
      this warning.
      
      Bug: v8:8735
      Change-Id: I5dd2dccf215a7fd2f6dd14993368cc5cbb6c71e5
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2080361Reviewed-by: 's avatarJakob Kummerow <jkummerow@chromium.org>
      Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
      Commit-Queue: Jakob Kummerow <jkummerow@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#68320}
      f08cbfdc
  31. 10 Jun, 2020 1 commit
  32. 28 May, 2020 1 commit
  33. 25 May, 2020 1 commit
  34. 13 May, 2020 1 commit
  35. 12 May, 2020 1 commit
    • Omer Katz's avatar
      heap,cppgc: Update StackState enum values · fff219bf
      Omer Katz authored
      This CL adds 2 new values to the EmbedderStackState enum with more
      explicit names. The old values are updated as aliases to the new
      values and marked as soon to be deprecated. This CL also moves the
      enum to v8-platform.h so that it can be reused by cppgc.
      
      Depracating individual values in an enum is supported by GCC only
      since version 6. Thus new macros were needed for the deprecation
      (which delegate to the existing macros when supported). GCC versions
      older than 6 are still used by the CQ bots.
      
      Bug: chromium:1056170
      Change-Id: Id1ea73edfbbae282b0d8a3bb103dbbbf8ebd417e
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2188971
      Commit-Queue: Omer Katz <omerkatz@chromium.org>
      Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
      Reviewed-by: 's avatarMichael Lippautz <mlippautz@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#67744}
      fff219bf