| /third_party/node/deps/v8/src/logging/ |
| D | counters-definitions.h | 15 HR(background_marking, V8.GCBackgroundMarking, 0, 10000, 101) \
16 HR(background_sweeping, V8.GCBackgroundSweeping, 0, 10000, 101) \
17 HR(code_cache_reject_reason, V8.CodeCacheRejectReason, 1, 6, 6) \
18 HR(errors_thrown_per_context, V8.ErrorsThrownPerContext, 0, 200, 20) \
19 HR(debug_feature_usage, V8.DebugFeatureUsage, 1, 7, 7) \
20 HR(incremental_marking_reason, V8.GCIncrementalMarkingReason, 0, \
22 HR(incremental_marking_sum, V8.GCIncrementalMarkingSum, 0, 10000, 101) \
23 HR(mark_compact_reason, V8.GCMarkCompactReason, 0, \
25 HR(gc_finalize_clear, V8.GCFinalizeMC.Clear, 0, 10000, 101) \
26 HR(gc_finalize_epilogue, V8.GCFinalizeMC.Epilogue, 0, 10000, 101) \
[all …]
|
| /third_party/node/deps/v8/infra/mb/ |
| D | mb_config.pyl | 1 # Copyright 2016 The V8 project authors. All rights reserved.
59 'V8 Linux - builder': 'release_x86_gcmole',
60 'V8 Linux - debug builder': 'debug_x86',
61 'V8 Linux - shared - builder': 'release_x86_shared_verify_heap',
62 'V8 Linux - noi18n - debug builder': 'debug_x86_no_i18n',
63 'V8 Linux - verify csa - builder': 'release_x86_verify_csa',
65 'V8 Linux64 - builder': 'release_x64',
66 'V8 Linux64 - builder (goma cache silo)': 'release_x64',
67 'V8 Linux64 - builder (reclient)': 'release_x64_reclient',
68 'V8 Linux64 - builder (reclient compare)': 'release_x64_reclient',
[all …]
|
| /third_party/node/doc/contributing/maintaining/ |
| D | maintaining-V8.md | 1 # Maintaining V8 in Node.js
5 V8 follows the Chromium release schedule. The support horizon for Chromium is
7 needs to support multiple versions of V8 longer than what upstream needs
8 to support. V8 branches in Node.js lack of an official maintenance process due
12 a workflow for maintaining the V8 branches in both Node.js LTS and current
13 releases, and discusses how the Node.js and V8 teams at Google can help.
15 ## V8 release schedule
17 V8 and Chromium follow a
19 there are several V8 branches that are **active**, see the
20 [V8 release process](https://v8.dev/docs/release-process). All older branches
[all …]
|
| /third_party/node/deps/v8/include/ |
| D | APIDesign.md | 1 # The V8 public C++ API
5 The V8 public C++ API aims to support four use cases:
7 1. Enable applications that embed V8 (called the embedder) to configure and run
8 one or more instances of V8.
11 4. Provide access to the V8 debugger (inspector).
13 # Configuring and running an instance of V8
15 V8 requires access to certain OS-level primitives such as the ability to
19 interface. While V8 bundles a basic implementation, embedders are highly
24 all instances of V8 should share one allocator.
27 further interactions with V8 should explicitly reference the v8::Isolate they
[all …]
|
| /third_party/node/deps/v8/infra/testing/ |
| D | builders.pyl | 1 # Copyright 2018 The V8 project authors. All rights reserved.
57 'V8 Fuchsia': {
852 'V8 Fuzzer': {
865 'V8 Linux': {
937 'V8 Linux - arm64 - sim - CFI': {
946 'V8 Linux - arm64 - sim - MSAN': {
955 'V8 Linux - debug': {
1055 'V8 Linux - full debug': {
1063 'V8 Linux - gc stress': {
1081 'V8 Linux - noi18n - debug': {
[all …]
|
| D | README.md | 4 specific bots on V8's continuous infrastructure (CI) or tryserver. Features to
10 The test specifications are defined in a V8-side python-literal file
44 V8 test driver.
82 V8 Linux64
83 V8 Linux64 - debug
95 V8 Linux64 - fyi
96 V8 Linux64 - debug - fyi
|
| /third_party/node/deps/v8/ |
| D | README.md | 1 V8 JavaScript Engine
4 V8 is Google's open source JavaScript engine.
6 V8 implements ECMAScript as specified in ECMA-262.
8 V8 is written in C++ and is used in Google Chrome, the open source
11 V8 can run standalone, or can be embedded into any C++ application.
13 V8 Project page: https://v8.dev/docs
23 This will checkout V8 into the directory `v8` and fetch all of its dependencies.
|
| /third_party/node/deps/v8/src/init/ |
| D | v8.cc | 41 v8::Platform* V8::platform_ = nullptr;
90 void V8::InitializePlatform(v8::Platform* platform) { in InitializePlatform()
107 bool V8::InitializeSandbox() { in InitializeSandbox()
122 void V8::Initialize() { in Initialize()
261 void V8::Dispose() { in Dispose()
278 void V8::DisposePlatform() { in DisposePlatform()
299 v8::Platform* V8::GetCurrentPlatform() { in GetCurrentPlatform()
306 void V8::SetPlatformForTesting(v8::Platform* platform) { in SetPlatformForTesting()
311 void V8::SetSnapshotBlob(StartupData* snapshot_blob) { in SetSnapshotBlob()
|
| /third_party/node/test/cctest/ |
| D | node_test_fixture.cc | 22 v8::V8::InitializePlatform(NodeZeroIsolateTestFixture::platform.get()); in SetUp()
24 ASSERT_TRUE(v8::V8::InitializeSandbox()); in SetUp()
28 v8::V8::Initialize(); in SetUp()
32 v8::V8::Dispose(); in TearDown()
33 v8::V8::DisposePlatform(); in TearDown()
|
| /third_party/node/deps/v8/tools/visual_studio/ |
| D | README.txt | 1 The Microsoft Visual Studio project files for including V8 in a Visual
5 V8 project. It contains the required infrastructure and a README.txt
9 project integrated V8 into the Windows build.
11 The main build system for V8 is still SCons, see the V8 wiki page
|
| /third_party/node/deps/v8/tools/v8.xcodeproj/ |
| D | README.txt | 1 The Xcode project for V8 has been retired. If an Xcode project
4 V8 project. It contains the required infrastructure and a README.txt
8 project integrated V8 into the Mac build.
10 The main build system for V8 is still SCons, see
|
| /third_party/node/test/embedding/ |
| D | embedtest.cc | 18 using v8::V8;
42 V8::InitializePlatform(platform.get()); in main()
43 V8::Initialize(); in main()
48 V8::Dispose(); in main()
49 V8::DisposePlatform(); in main()
|
| /third_party/node/deps/v8/tools/cppgc/ |
| D | copy.bara.sky | 1 # Copyright 2020 the V8 project authors. All rights reserved.
24 # This workflow syncs cppgc source inside V8's googlesource repo with GitHub.
36 authoring=authoring.pass_thru('V8 Team <v8-dev@googlegroups.com>'),
38 metadata.squash_notes(prefix='Export of V8 changes from ' +
|
| /third_party/node/ |
| D | common.gypi | 5 'werror': '', # Turn off -Werror in V8 build.
6 'visibility%': 'hidden', # V8's visibility setting
9 'want_separate_host_toolset%': 0, # V8 should not build target and host
11 'component%': 'static_library', # NB. these names match with what V8 expects
12 'msvs_multi_core_compile': '0', # we do enable multicore compiles, but not using the V8 way
34 # Don't use ICU data file (icudtl.dat) from V8, we use our own.
37 # Reset this number to 0 on major V8 upgrades.
41 ##### V8 defaults for Node.js #####
46 # These are more relevant for V8 internal development.
49 # Enable compiler warnings when using V8_DEPRECATED apis from V8 code.
[all …]
|
| /third_party/node/deps/v8/tools/v8windbg/ |
| D | README.md | 3 V8windbg is a WinDbg extension for the V8 engine. It adjusts the behavior of the
5 inspecting V8 object types. It is intended to be as robust as possible in dumps
16 extension. To inspect V8 objects, use the Locals window or the `dx` command as
26 containing V8.
35 - `@$v8object()` returns information about the fields of a tagged V8 value,
59 avoid depending on V8 internals.
62 extension. The V8-specific implementation under `./src` then implements the two
74 show fields within V8 objects.
75 - `v8-debug-helper-interop.{cc,h}` makes requests to the V8 postmortem debugging
82 - It registers a "parent model" for all known V8 object types, such as
[all …]
|
| /third_party/node/deps/v8/tools/debug_helper/ |
| D | README.md | 1 # V8 debug helper
3 This library is for debugging V8 itself, not debugging JavaScript running within
4 V8. It is designed to be called from a debugger extension running within a
|
| /third_party/node/deps/v8/tools/clusterfuzz/foozzie/testdata/ |
| D | smoke_test_output.txt | 2 # V8 correctness failure
3 # V8 correctness configs: x64,ignition:x64,ignition_turbo
4 # V8 correctness sources: smoke test failed
5 # V8 correctness suppression:
|
| D | failure_output_arch.txt | 2 # V8 correctness failure
3 # V8 correctness configs: x64,ignition:x64,ignition_turbo
4 # V8 correctness sources: f60
5 # V8 correctness suppression:
|
| D | failure_output_second.txt | 2 # V8 correctness failure
3 # V8 correctness configs: x64,ignition:ia32,ignition_turbo
4 # V8 correctness sources: f60
5 # V8 correctness suppression:
|
| D | failure_output.txt | 2 # V8 correctness failure
3 # V8 correctness configs: x64,ignition:x64,ignition_turbo
4 # V8 correctness sources: f60
5 # V8 correctness suppression:
|
| /third_party/node/deps/v8/bazel/config/ |
| D | v8-target-cpu.bzl | 1 # Copyright 2021 the V8 project authors. All rights reserved.
10 doc = "A singleton provider that specifies the V8 target CPU type",
12 "value": "The V8 Target CPU selected.",
28 doc = "CPU that V8 will generate code for.",
|
| /third_party/node/deps/v8/tools/torque/vim-torque/ |
| D | README.md | 1 # V8 Torque syntax support for vim
3 This plugin adds syntax highlighting support for the V8 Torque domain-specific
15 ln -s $V8/tools/torque/vim-torque ~/.vim/bundle/vim-torque
|
| /third_party/node/doc/contributing/ |
| D | node-postmortem-support.md | 6 provides this metadata in its builds for V8 and Node.js internal structures.
8 ## V8 postmortem metadata
10 V8 prefixes all postmortem constants with `v8dbg_`, and they allow inspection of
11 objects on the heap as well as object properties and references. V8 generates
18 V8 constants by providing ways to inspect Node.js-specific structures, like
|
| /third_party/node/deps/v8/src/snapshot/ |
| D | mksnapshot.cc | 240 v8::V8::InitializeICUDefaultLocation(argv[0]); in main()
242 v8::V8::InitializePlatform(platform.get()); in main()
244 if (!v8::V8::InitializeSandbox()) { in main()
248 v8::V8::Initialize(); in main()
310 v8::V8::Dispose(); in main()
311 v8::V8::DisposePlatform(); in main()
|
| /third_party/node/tools/snapshot/ |
| D | README.md | 3 This is the V8 startup snapshot builder of Node.js. Not to be confused with
4 V8's own snapshot builder, which builds a snapshot containing JavaScript
6 deserialized on top of V8's own startup snapshot. When Node.js is launched,
21 In the default build of the Node.js executable, to embed a V8 startup snapshot
|