- 22 Jan, 2020 1 commit
-
-
Clemens Backes authored
This API was used for IndexedDB support and for transferring modules by serializing and deserializing (before we were sharing code between isolates). Last uses were removed in https://crrev.com/c/1847366, thus this whole API is unused by now. This CL deprecates the API and refactors tests to use the internal APIs instead. R=adamk@chromium.org Bug: v8:10146 Change-Id: I838039b4be7ea4eebe6769f31f48e51e7bcd4645 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2006090 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by:
Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/master@{#65908}
-
- 21 Jan, 2020 1 commit
-
-
Clemens Backes authored
There is not really a reason to guard the first by the latter. Just emit a hint if --trace-liftoff is used without --trace-wasm-decoder, but still make it work. Also, used DEFINE_DEBUG_BOOL instead of guarding the output by another "#ifdef DEBUG". R=ahaas@chromium.org Change-Id: Ia7d3f504df92779447877612e98b9c2a847b9f6b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2011828Reviewed-by:
Andreas Haas <ahaas@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#65894}
-
- 17 Jan, 2020 1 commit
-
-
Dominik Inführ authored
Split the linked list of array buffer extensions into two lists for young and old JSArrayBuffers. Process young extensions during the minor GC pause. When promoting JSArrayBuffers into the old gen, move the extension into the old linked list as well. Bug: v8:10064 Change-Id: I07275ffe7ba918c9b2d6d0648a6d1b59e4fa4891 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1997438 Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#65842}
-
- 16 Jan, 2020 1 commit
-
-
Pierre Langlois authored
We had a --log-instruction-stats option which would count executed instructions, splitting them into categories. We haven't used this for some years so we're proposing to just remove the code so it doesn't bitrot and allows further cleanups. Change-Id: If24d11608823e24689ea02f09f5e93b4a5acd636 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2002819Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Commit-Queue: Pierre Langlois <pierre.langlois@arm.com> Cr-Commit-Position: refs/heads/master@{#65826}
-
- 14 Jan, 2020 2 commits
-
-
Clemens Backes authored
This just removes the flag if it is not supported anyway. This avoids fuzzers trapping over this. The same was done for the --perf-prof flag in https://crrev.com/c/1993969. R=ahaas@chromium.org Bug: chromium:1035233 Change-Id: I7b4b8fdd141df717cc62d795534f30435f7b38c1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1998083Reviewed-by:
Andreas Haas <ahaas@chromium.org> Reviewed-by:
Maya Lekova <mslekova@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#65760}
-
Clemens Backes authored
Tests which set the --perf-prof flag leave behind a file in the current working directory every time they execute. In order to avoid this, this CL introduces a --perf-prof-delete-file flag, which removes this file right after creating it. This still allows the process to write to it via the open handle, but the file will be gone afterwards, even if the process crashes or gets killed while executing. R=ahaas@chromium.org Bug: v8:10121 Change-Id: I99b159bb6d94255f77095ac78d98ba55106e94fc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2000738Reviewed-by:
Andreas Haas <ahaas@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#65759}
-
- 13 Jan, 2020 1 commit
-
-
Pierre Langlois authored
Simulator-specific instructions are very useful, we can: - Place breakpoints that enable the simulator's interactive debugger, allowing us to see registers, the stack and print JS objects. - Enable and disable simulator tracing dynamically. - Call printf() directly, as the simulator cannot easily support its calling convention. However these tools are not available when generating builtins. The reason is that when cross-compiling, builtins are generated for real hardware but may still run inside the simulator on the host if we have a custom snapshot. Using the `v8_embed_script` GN option will do that for example but embedders may also do this with the V8 API. mksnapshot cannot tell the difference between generating code for a simulator build and a cross-build. If we change this, we can allow us to use simulator-specific features in builtins in simulator builds. So in this patch we: - Introduce a --target_is_simulator mksnapshot flag to drive the enable_simulator_code Assembler option. - Make sure the assembler respect the option instead of the USE_SIMULATOR macro. Change-Id: I7a7249f514427c1a2518a1af3679679596a72c7e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1991497Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Commit-Queue: Pierre Langlois <pierre.langlois@arm.com> Cr-Commit-Position: refs/heads/master@{#65734}
-
- 10 Jan, 2020 2 commits
-
-
Clemens Backes authored
The fuzzers picked up this flag, and are now complaining that they run into UNREACHABLE/FATAL too often because the {PerfJitLogger} is not implemented on non-linux platforms. This CL removes the flag if it's not supported, so users get a warning about the unknown flag, but otherwise it's ignored. This should unblock the fuzzers, and slightly reduces binary size on non-linux. R=ahaas@chromium.org Bug: chromium:1035233 Change-Id: I6b9282318bc82ff23173bc83ae31cb2d8cbdcdb7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1993969 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by:
Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#65695}
-
Jakob Kummerow authored
This patch maintains the previous default value of the flag controlling the max size of Wasm memories, but allows the limit to be raised on the command line. Bonus content: improve the multi-mapped mock allocator by falling back to regular allocation for small requests. More bonus content: make debug-mode Wasm tests faster. Bug: v8:6306 Change-Id: Idabae5734794b06e65d45b3a6165dbd488847f3f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1981157 Auto-Submit: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
Clemens Backes <clemensb@chromium.org> Reviewed-by:
Andreas Haas <ahaas@chromium.org> Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#65681}
-
- 09 Jan, 2020 1 commit
-
-
Ulan Degenbaev authored
This changes the marking worklist draining for the main thread marker and the concurrent marker to use the following algorithm in per-context mode: 1) Pop an object from the marking worklist. 2) Try to infer the native context that owns the objects. This is done using a new NativeContextInferrer class. 3) If the inference is successful, then change the active marking worklist to the worklist of the inferred native context. 4) Otherwise, keep the current active marking worklist. 5) Visit the object. Newly discovered objects will be pushed onto the active marking worklist. 6) Account the object size for the native context corresponding to the active marking worklist. This is done using a new NativeContextStats class. The main property of the algorithm is that each object for which we couldn't infer the native context is either attributed to the native context retaining it or is not attributed to any native context. Bug: chromium:973627 Change-Id: Ide4ab992275d115279f971d89ace657f4c05e176 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1981491 Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
Dominik Inführ <dinfuehr@chromium.org> Cr-Commit-Position: refs/heads/master@{#65663}
-
- 08 Jan, 2020 3 commits
-
-
Clemens Backes authored
For finching Liftoff on mobile, we want to support Liftoff-only, TurboFan-only, and Liftoff with tier-up to TurboFan. Hence, chrome needs to be able to set the liftoff flag separately from the tier-up flag, and there should not be an implication, since that implication would be applied before all flags have been set to their final state. See https://crrev.com/c/1988360 for the chromium-side change. Note that this CL does not change any defaults. After this change, Liftoff can be disabled by passing '--no-liftoff', independent of the tier-up flag (this would be a TurboFan-only configuration). A Liftoff-only version would specify --liftoff and --no-wasm-tier-up. The default on Desktop (--liftoff and --wasm-tier-up) compiles with Liftoff first, and tiers up to TurboFan. R=ahaas@chromium.org Bug: chromium:1040061 Change-Id: I0291ec20f5a29f3a9e23c25c93907d1d8ffabd51 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1988548Reviewed-by:
Andreas Haas <ahaas@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#65635}
-
Maya Lekova authored
Put the nesting limit of the serializer back to 25. Bug: chromium:1034768 Change-Id: I7ea827d27241ea930bae40142069bab1962e4133 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1981156 Commit-Queue: Maya Lekova <mslekova@chromium.org> Reviewed-by:
Michael Stanton <mvstanton@chromium.org> Cr-Commit-Position: refs/heads/master@{#65630}
-
Frank Tang authored
I2S https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/vE4i42C2MUs/Sb804J3fBQAJ I2I https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/muRQBwyzzPw/FgdwgcbnAgAJ Design Doc: https://shorturl.at/emEHW Chrome Status: https://www.chromestatus.com/feature/4965112605573120 Latest spec: https://tc39.es/proposal-intl-displaynames/ Spec Github: https://github.com/tc39/proposal-intl-displaynames LGTMs: bratell.d@gmail.com / chrishtr@chromium.org / yoav@yoav.ws Bug: v8:8703 Change-Id: Iaf4f94d813fa742989ab149420d07f6f6f523443 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1982802 Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#65620}
-
- 07 Jan, 2020 1 commit
-
-
Tobias Tebbi authored
This reverts commit a3039123. Reason for revert: https://crrev.com/c/1985990 should fix the root-cause now. Original change's description: > [regalloc] temporarily disable control-flow aware allocation > > Bug: v8:10077 > > Change-Id: I4b76d62462658dfa54f351ba10e52e57f63f3493 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1977857 > Commit-Queue: Tobias Tebbi <tebbi@chromium.org> > Reviewed-by: Thibaud Michaud <thibaudm@chromium.org> > Cr-Commit-Position: refs/heads/master@{#65536} TBR=tebbi@chromium.org,thibaudm@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: v8:10077 Change-Id: I356f1cc8d70f1f9efdbc72e3398cc830c51b664d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1986002Reviewed-by:
Tobias Tebbi <tebbi@chromium.org> Commit-Queue: Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/master@{#65608}
-
- 27 Dec, 2019 1 commit
-
-
Mike Stanton authored
Renderer hangs are possible with current limit (25). I'd like to know what a limit of 15 does to benchmark performance, and see it's effect on hangs. Bug: chromium:1034768 Change-Id: Ie7fae638972816f547e6ca7a9d7f199cbcf6b2cc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1981492Reviewed-by:
Michael Stanton <mvstanton@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Michael Stanton <mvstanton@chromium.org> Cr-Commit-Position: refs/heads/master@{#65564}
-
- 20 Dec, 2019 2 commits
-
-
Frank Tang authored
I2I https://mail.google.com/mail/u/0/#search/Intl.DisplayNames+Intent/KtbxLwgxBjLmZRWGMwZfjnVwNFvdndwvBq Design Doc: https://shorturl.at/emEHW https://www.chromestatus.com/feature/4965112605573120 Latest spec: https://tc39.es/proposal-intl-displaynames/ Spec Github: https://github.com/tc39/proposal-intl-displaynames Bug: v8:8703 Change-Id: I3757d2131029104984d26cd5f037f90dd7b136e8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1976903Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Frank Tang <ftang@chromium.org> Cr-Commit-Position: refs/heads/master@{#65544}
-
Tobias Tebbi authored
Bug: v8:10077 Change-Id: I4b76d62462658dfa54f351ba10e52e57f63f3493 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1977857 Commit-Queue: Tobias Tebbi <tebbi@chromium.org> Reviewed-by:
Thibaud Michaud <thibaudm@chromium.org> Cr-Commit-Position: refs/heads/master@{#65536}
-
- 19 Dec, 2019 1 commit
-
-
Frank Tang authored
To sync with https://github.com/tc39/proposal-intl-displaynames/pull/63 Bug: v8:10069 Change-Id: I64921c348a69ca7b265d498cac9e7da9f3e3f755 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1975038Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Frank Tang <ftang@chromium.org> Cr-Commit-Position: refs/heads/master@{#65530}
-
- 18 Dec, 2019 1 commit
-
-
Sigurd Schneider authored
This CL adds an argument to the heap profiler that allows to control whether global objects (e.g. 'window' in JavaScript) are treated as roots in the heap snapshot. Doing so hides blink-internal details and is often a good choice when user-JS leaks are investigated. Sometimes, however, this introduces spurious retainer cycles, which are hard to debug. Previously, this option was exposed as a V8 flag. The blink implications of the build-time V8 flag are now available via the new blink flag `enable_additional_blink_object_names`. Tbr: hpayer@chromium.org Bug: chromium:1034504 Change-Id: Ibe9412917ae598a3ff0c3dc956ab0bc179f50a21 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1967387Reviewed-by:
Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#65491}
-
- 17 Dec, 2019 3 commits
-
-
Maya Lekova authored
Add a --max-serializer-nesting flag which defaults to 25. Fixed: chromium:1034768 Change-Id: Ib68f26ce4bf53db297b25d16a046d275beaec642 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1969895 Commit-Queue: Maya Lekova <mslekova@chromium.org> Reviewed-by:
Michael Stanton <mvstanton@chromium.org> Cr-Commit-Position: refs/heads/master@{#65486}
-
Zhang, Shiyu authored
This is a reland of 5f5b4b04 Original change's description: > Support Intel VTune ITT API > > Add VTune domain support extension to use VTune Domain/Task API and > tagging trace data for particular JS code block. > > How to use: > 1. Set `"checkout_ittapi" = True` in the custom_vars section of .gclient > file to download intel/ittapi by 'gclient sync' > 2. Build d8 with gn build flag 'v8_enable_vtunetracemark = true' > 3. Run d8 with flag '--enable-vtune-domain-support' > > The Vtune Domain/Task API can be invoked from JS to mark JS code block. > You can mark the start of a JS task by > vtunedomainmark(domain_name, task_name, "start") > and the end of a task by > vtunedomainmark(domain_name, task_name, "end") > Tasks can nest. > > The VTune API (ittapi) is integrated as an external third party library > while the v8_vtune_jit also relies on the VTune ittapi. We have another > patch almost ready which refactors the v8_vtune_jit related code to > depend on the third_party/ittapi. We will submit the refactored v8_vtune_jit > code after this patch stabilized and landed. > > > Contributed by fanchen.kong@intel.com > > Change-Id: I0ecc9dd4e1ea52545f1b6932fcdadfa7c1a6d2b2 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1938490 > Commit-Queue: Shiyu Zhang <shiyu.zhang@intel.com> > Reviewed-by: Hannes Payer <hpayer@chromium.org> > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Cr-Commit-Position: refs/heads/master@{#65409} Change-Id: I563aa70fa2b8abe34c981af47aa7220cfc2a7edb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1963511 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#65478}
-
Dominik Inführ authored
Add pointer-sized field extension to the JSArrayBuffer class. Only reserve space for this field when feature is enabled for now. Bug: v8:10064 Change-Id: Idb6fdcdce2a048e6aed9a892bc46ce029e1119f3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1956166Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Cr-Commit-Position: refs/heads/master@{#65471}
-
- 13 Dec, 2019 1 commit
-
-
Jakob Kummerow authored
This new testing allocator for ArrayBuffers uses a small real allocation that is repeatedly mapped into the requested allocation size. Its purpose is to allow testing of huge TypedArrays without actually consuming a huge amount of memory, at the expense of correct behavior (elements will alias each other). It is only supported on Linux for now, and of course off by default. Bug: v8:4153 Change-Id: I4917a78b6190dc075dc4614ebe2696e63addc8c2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1962270 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#65444}
-
- 11 Dec, 2019 3 commits
-
-
Joshua Litt authored
This reverts commit 7e632f57. Reason for revert: clusterfuzzed Bug: chromium:1032906 Original change's description: > Reland "[replaceAll] Stage String.prototype.replaceAll." > > This reverts commit 3114000a. > > Reason for revert: Clusterfuzz issue should be fixed. > > Original change's description: > > Revert "[replaceAll] Stage String.prototype.replaceAll." > > > > This reverts commit 825f65d3. > > > > Reason for revert: Clusterfuzzed > > Bug: chromium:1028475 > > > > Original change's description: > > > [replaceAll] Stage String.prototype.replaceAll. > > > > > > Intent to ship thread: > > > https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/raep1X9R_SE > > > > > > Bug: v8:9801 > > > Change-Id: I61c559b82b4119084420ffb0a14a27774e37c760 > > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1930608 > > > Reviewed-by: Adam Klein <adamk@chromium.org> > > > Commit-Queue: Joshua Litt <joshualitt@chromium.org> > > > Cr-Commit-Position: refs/heads/master@{#65161} > > > > TBR=adamk@chromium.org,joshualitt@chromium.org > > > > Change-Id: I7fa44eda475b8f421f74491e60a3131d381eb789 > > No-Presubmit: true > > No-Tree-Checks: true > > No-Try: true > > Bug: v8:9801 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1935024 > > Reviewed-by: Joshua Litt <joshualitt@chromium.org> > > Commit-Queue: Joshua Litt <joshualitt@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#65175} > > TBR=adamk@chromium.org,joshualitt@chromium.org > > # Not skipping CQ checks because original CL landed > 1 day ago. > > Bug: chromium:1028475, v8:9801 > Change-Id: Idb5fbd1ec38084222357aeb2d9ff05d703f10eb5 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1946737 > Reviewed-by: Joshua Litt <joshualitt@chromium.org> > Reviewed-by: Adam Klein <adamk@chromium.org> > Commit-Queue: Joshua Litt <joshualitt@chromium.org> > Cr-Commit-Position: refs/heads/master@{#65308} TBR=adamk@chromium.org,joshualitt@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: chromium:1028475, v8:9801 Change-Id: I17dd634cac7b11d4db8d24ec30be10c06dea757b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1961941Reviewed-by:
Joshua Litt <joshualitt@chromium.org> Commit-Queue: Joshua Litt <joshualitt@chromium.org> Cr-Commit-Position: refs/heads/master@{#65414}
-
Maya Lekova authored
This reverts commit 5f5b4b04. Reason for revert: Breaks vtunejit bot - see https://ci.chromium.org/p/v8/builders/ci/V8%20Linux%20-%20vtunejit/32958 Original change's description: > Support Intel VTune ITT API > > Add VTune domain support extension to use VTune Domain/Task API and > tagging trace data for particular JS code block. > > How to use: > 1. Set `"checkout_ittapi" = True` in the custom_vars section of .gclient > file to download intel/ittapi by 'gclient sync' > 2. Build d8 with gn build flag 'v8_enable_vtunetracemark = true' > 3. Run d8 with flag '--enable-vtune-domain-support' > > The Vtune Domain/Task API can be invoked from JS to mark JS code block. > You can mark the start of a JS task by > vtunedomainmark(domain_name, task_name, "start") > and the end of a task by > vtunedomainmark(domain_name, task_name, "end") > Tasks can nest. > > The VTune API (ittapi) is integrated as an external third party library > while the v8_vtune_jit also relies on the VTune ittapi. We have another > patch almost ready which refactors the v8_vtune_jit related code to > depend on the third_party/ittapi. We will submit the refactored v8_vtune_jit > code after this patch stabilized and landed. > > > Contributed by fanchen.kong@intel.com > > Change-Id: I0ecc9dd4e1ea52545f1b6932fcdadfa7c1a6d2b2 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1938490 > Commit-Queue: Shiyu Zhang <shiyu.zhang@intel.com> > Reviewed-by: Hannes Payer <hpayer@chromium.org> > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Cr-Commit-Position: refs/heads/master@{#65409} TBR=machenbach@chromium.org,hpayer@chromium.org,verwaest@chromium.org,shiyu.zhang@intel.com Change-Id: I44a6e5b1aa32e753ae41966ed321ed787cc752f8 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1960291Reviewed-by:
Maya Lekova <mslekova@chromium.org> Commit-Queue: Maya Lekova <mslekova@chromium.org> Cr-Commit-Position: refs/heads/master@{#65410}
-
Zhang, Shiyu authored
Add VTune domain support extension to use VTune Domain/Task API and tagging trace data for particular JS code block. How to use: 1. Set `"checkout_ittapi" = True` in the custom_vars section of .gclient file to download intel/ittapi by 'gclient sync' 2. Build d8 with gn build flag 'v8_enable_vtunetracemark = true' 3. Run d8 with flag '--enable-vtune-domain-support' The Vtune Domain/Task API can be invoked from JS to mark JS code block. You can mark the start of a JS task by vtunedomainmark(domain_name, task_name, "start") and the end of a task by vtunedomainmark(domain_name, task_name, "end") Tasks can nest. The VTune API (ittapi) is integrated as an external third party library while the v8_vtune_jit also relies on the VTune ittapi. We have another patch almost ready which refactors the v8_vtune_jit related code to depend on the third_party/ittapi. We will submit the refactored v8_vtune_jit code after this patch stabilized and landed. Contributed by fanchen.kong@intel.com Change-Id: I0ecc9dd4e1ea52545f1b6932fcdadfa7c1a6d2b2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1938490 Commit-Queue: Shiyu Zhang <shiyu.zhang@intel.com> Reviewed-by:
Hannes Payer <hpayer@chromium.org> Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/master@{#65409}
-
- 03 Dec, 2019 1 commit
-
-
Joshua Litt authored
This reverts commit 3114000a. Reason for revert: Clusterfuzz issue should be fixed. Original change's description: > Revert "[replaceAll] Stage String.prototype.replaceAll." > > This reverts commit 825f65d3. > > Reason for revert: Clusterfuzzed > Bug: chromium:1028475 > > Original change's description: > > [replaceAll] Stage String.prototype.replaceAll. > > > > Intent to ship thread: > > https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/raep1X9R_SE > > > > Bug: v8:9801 > > Change-Id: I61c559b82b4119084420ffb0a14a27774e37c760 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1930608 > > Reviewed-by: Adam Klein <adamk@chromium.org> > > Commit-Queue: Joshua Litt <joshualitt@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#65161} > > TBR=adamk@chromium.org,joshualitt@chromium.org > > Change-Id: I7fa44eda475b8f421f74491e60a3131d381eb789 > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: v8:9801 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1935024 > Reviewed-by: Joshua Litt <joshualitt@chromium.org> > Commit-Queue: Joshua Litt <joshualitt@chromium.org> > Cr-Commit-Position: refs/heads/master@{#65175} TBR=adamk@chromium.org,joshualitt@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: chromium:1028475, v8:9801 Change-Id: Idb5fbd1ec38084222357aeb2d9ff05d703f10eb5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1946737Reviewed-by:
Joshua Litt <joshualitt@chromium.org> Reviewed-by:
Adam Klein <adamk@chromium.org> Commit-Queue: Joshua Litt <joshualitt@chromium.org> Cr-Commit-Position: refs/heads/master@{#65308}
-
- 28 Nov, 2019 1 commit
-
-
Dan Elphick authored
If V8_SHARED_RO_HEAP is set, then GetSharedMemoryStatistics now reports the size of RO_SPACE. Additionally size values for RO_SPACE are zeroed in the per-isolate Heap and Space stats. Bug: v8:7464 Change-Id: I2d6843c001b55974460d1df034f08d1ed5b0d8da Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1900459 Commit-Queue: Dan Elphick <delphick@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#65231}
-
- 27 Nov, 2019 3 commits
-
-
Joshua Litt authored
This reverts commit bd9efe1f. Reason for revert: clusterfuzz Bug: chromium:1029174 Original change's description: > [regexp] Stage match indices. > > Bug: v8:9548 > Change-Id: Id6be43433b12733e39db712559715ba30e681059 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1935207 > Commit-Queue: Joshua Litt <joshualitt@chromium.org> > Reviewed-by: Jakob Gruber <jgruber@chromium.org> > Cr-Commit-Position: refs/heads/master@{#65218} TBR=adamk@chromium.org,jgruber@chromium.org,joshualitt@chromium.org Change-Id: I098385e2dcebc7bfacd91312bcebfdb889b3d0ca No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:9548 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1941137Reviewed-by:
Joshua Litt <joshualitt@chromium.org> Commit-Queue: Joshua Litt <joshualitt@chromium.org> Cr-Commit-Position: refs/heads/master@{#65222}
-
Joshua Litt authored
Bug: v8:9548 Change-Id: Id6be43433b12733e39db712559715ba30e681059 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1935207 Commit-Queue: Joshua Litt <joshualitt@chromium.org> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#65218}
-
Mythri A authored
Enabling concurrent inlining builds the graph on background thread reducing the time spent on main thread. Bug: v8:9684 Change-Id: Iee00aa991ab8e14fad76b0d9c0b0fd9f8d1eecde Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1937149Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Commit-Queue: Mythri Alle <mythria@chromium.org> Cr-Commit-Position: refs/heads/master@{#65202}
-
- 26 Nov, 2019 2 commits
-
-
Joshua Litt authored
This reverts commit 825f65d3. Reason for revert: Clusterfuzzed Bug: chromium:1028475 Original change's description: > [replaceAll] Stage String.prototype.replaceAll. > > Intent to ship thread: > https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/raep1X9R_SE > > Bug: v8:9801 > Change-Id: I61c559b82b4119084420ffb0a14a27774e37c760 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1930608 > Reviewed-by: Adam Klein <adamk@chromium.org> > Commit-Queue: Joshua Litt <joshualitt@chromium.org> > Cr-Commit-Position: refs/heads/master@{#65161} TBR=adamk@chromium.org,joshualitt@chromium.org Change-Id: I7fa44eda475b8f421f74491e60a3131d381eb789 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:9801 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1935024Reviewed-by:
Joshua Litt <joshualitt@chromium.org> Commit-Queue: Joshua Litt <joshualitt@chromium.org> Cr-Commit-Position: refs/heads/master@{#65175}
-
Georg Neis authored
This flag has had no effect since mid 2017 when its use-site was accidentally removed (in https://codereview.chromium.org/2902533003). Change-Id: I81436b064c2664deff781ad6d75ad47937e3fdc0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1934333 Auto-Submit: Georg Neis <neis@chromium.org> Reviewed-by:
Mythri Alle <mythria@chromium.org> Reviewed-by:
Michael Stanton <mvstanton@chromium.org> Commit-Queue: Michael Stanton <mvstanton@chromium.org> Cr-Commit-Position: refs/heads/master@{#65172}
-
- 25 Nov, 2019 1 commit
-
-
Joshua Litt authored
Intent to ship thread: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/raep1X9R_SE Bug: v8:9801 Change-Id: I61c559b82b4119084420ffb0a14a27774e37c760 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1930608Reviewed-by:
Adam Klein <adamk@chromium.org> Commit-Queue: Joshua Litt <joshualitt@chromium.org> Cr-Commit-Position: refs/heads/master@{#65161}
-
- 22 Nov, 2019 1 commit
-
-
Steve Blackburn authored
This CL adds build flags for pluging in third-party heap implementation. Additionally it redirects allocation requests when the flags are on. Bug: v8:9533 Change-Id: I7ef300ca9dc2b5f498a13211611ae4b4b3df8fa0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1928860 Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
Igor Sheludko <ishell@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#65114}
-
- 21 Nov, 2019 1 commit
-
-
Mythri A authored
Make --turboprop imply a lower interrupt budget (10 * k). Bug: v8:9684 Change-Id: I6e4bac1a77755e5bc8c7433503fe985cbc6db7ff Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1928859Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Commit-Queue: Mythri Alle <mythria@chromium.org> Cr-Commit-Position: refs/heads/master@{#65101}
-
- 18 Nov, 2019 1 commit
-
-
Frank Tang authored
Design Doc https://shorturl.at/emEHW I2I: http://shorturl.at/pKRUV Bug: v8:8703 Change-Id: I9573b2ee6f1dce4dc594aa1df2753095f45af15e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1848683Reviewed-by:
Yang Guo <yangguo@chromium.org> Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Frank Tang <ftang@chromium.org> Cr-Commit-Position: refs/heads/master@{#65021}
-
- 11 Nov, 2019 1 commit
-
-
Dominik Inführ authored
This reverts commit 5e97378f. Reason for revert: Caused multiple regressions. Original change's description: > [heap] Promote young objects by default in MC > > Start experiment to promote all young live objects during mark-compact. > > The last CL https://crrev.com/c/1879938 got reverted because of a flaky > test, see v8:9192. > > Change-Id: I16897f45fffeafbb7e70c21899976a4c026e69ba > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1903432 > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> > Cr-Commit-Position: refs/heads/master@{#64832} TBR=ulan@chromium.org,dinfuehr@chromium.org Bug: chromium:1023308, chromium:1022708 # Not skipping CQ checks because original CL landed > 1 day ago. Change-Id: Ie551f0765fb54a36e52c20da8b026e2c0ebf0451 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1906385Reviewed-by:
Dominik Inführ <dinfuehr@chromium.org> Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Cr-Commit-Position: refs/heads/master@{#64882}
-
- 07 Nov, 2019 2 commits
-
-
Santiago Aboy Solanes authored
Since the turbo_decompression_elimination flag is removed, there are several methods in machine-type.h that get simplified, e.g TypeCompressedTaggedPointer() can be replaced by just "TaggedPointer()". Also Removing the creation of Change to/from Compressed nodes. Removing these Change nodes' logic is left to a follow-up CL. Bug: v8:7703 Change-Id: Iff1f9aa8361189cf781a26317fd342b942fd5aa4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1897537 Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org> Reviewed-by:
Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/master@{#64834}
-
Dominik Inführ authored
Start experiment to promote all young live objects during mark-compact. The last CL https://crrev.com/c/1879938 got reverted because of a flaky test, see v8:9192. Change-Id: I16897f45fffeafbb7e70c21899976a4c026e69ba Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1903432Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Cr-Commit-Position: refs/heads/master@{#64832}
-