- 26 Mar, 2019 6 commits
-
-
Georg Neis authored
We don't normally generate code for that. R=jarin@chromium.org Bug: v8:7790 Change-Id: Icd8b61e894b721ac44fd1d79d2460def9c8c5af3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1535824 Commit-Queue: Georg Neis <neis@chromium.org> Reviewed-by:
Jaroslav Sevcik <jarin@chromium.org> Cr-Commit-Position: refs/heads/master@{#60457}
-
Sigurd Schneider authored
Bug: v8:9020 Change-Id: Ieeec2b237b0531a84ea71dc53d24444c3425dda7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1538130Reviewed-by:
Peter Marshall <petermarshall@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#60456}
-
Benedikt Meurer authored
The details of the TurboFan pipeline stages are probably not relevant to most users of the "disabled-by-default-v8.compile" category, so we now log them to "disabled-by-default-v8.turbofan" category instead. Bug: v8:8598, v8:9039 Change-Id: Ib451f163f74eb11ffbeb0dc6f2ee590208bd296b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1538135 Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Jaroslav Sevcik <jarin@chromium.org> Reviewed-by:
-
Michael Lippautz authored
The flag has been replaced by v8_enable_raw_heap_snapshots. Bug: chromium:936797 Change-Id: I2466c6636c462fe49a090dc3c262c80fc40d783f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1532329 Auto-Submit: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/625ee00..aee5bb4 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/347c5e4..85ead57 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/ba35c7f..e17d1ed Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/ad70d89..23688af TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: I291cce7855a51614bde1d858e3705db03235cbed Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1539276Reviewed-by:
v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#60453}
-
Frank Tang authored
Force to use locale with extension if the created NumberFormat is not a DecimalFormat. Check the dynamic class id. Guard DecimalFormat casting code Bug: v8:9035 Change-Id: Id32a3f652b93ddfca82f95f30ad2107b364ee7fc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1536571Reviewed-by:
Sathya Gunasekaran <gsathya@chromium.org> Commit-Queue: Frank Tang <ftang@chromium.org> Cr-Commit-Position: refs/heads/master@{#60452}
-
- 25 Mar, 2019 33 commits
-
-
Cliff Smolinsky authored
The only use of shlwapi is for a single method which can be easily replaced by simple wstring calls. This change makes that swap and removes the reference to shlwapi completely. Bug: v8:9031 Change-Id: Ia8f2c44e8166d93e309016896b26a84bdb90d720 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1534960Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Cliff Smolinsky <cliffsmo@microsoft.com> Cr-Commit-Position: refs/heads/master@{#60451}
-
Mythri authored
Allocate feedback vectors lazily when the function's interrupt budget has reached a specified threshold. This cl introduces a new field in the ClosureFeedbackCellArray to track the interrupt budget for allocating feedback vectors. Using the interrupt budget on the bytecode array could cause problems when there are closures across native contexts and we may delay allocating feedback vectors in one of them causing unexpected performance cliffs. In the long term we may want to remove interrupt budget from bytecode array and use context specific budget for tiering up decisions as well. Bug: v8:8394 Change-Id: Ia8fbb71f5e8543a92f14c44aa762973da82d445c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1520719 Commit-Queue: Mythri Alle <mythria@chromium.org> Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#60450}
-
Igor Sheludko authored
Bug: chromium:913943 Change-Id: I2f7774ca1ea0a7855620a99d7e26cd764260129b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1538124 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/master@{#60449}
-
Benedikt Meurer authored
This adds OBJECT/SNAPSHOT trace events for Script and SharedFunctionInfo objects, logging their creation with appropriate information to make sense of them. Based on that we introduces five flow events to model the optimized compilation via tracing in the "disabled-by-default-v8.compile" category: - "v8.optimizingCompile.start" logs the creation of the PipelineCompilationJob (for TurboFan JavaScript optimization) with the "function" argument referring to the trace event object created for the SharedFunctionInfo. - "v8.optimzingCompile.prepare" logs the preparation of the PipelineCompilationJob on the main thread, also carrying the "function" argument. This connects the flow event to the actual tracing duration event associated with the preparation phases. - "v8.optimizingCompile.execute" logs the (usually concurrent) optimization of the TurboFan graph (again with "function"). - "v8.optimizingCompile.finalize" logs the main thread phase which finalizes the optimized code and eventually installs it (in case of success). - "v8.optimizingCompile.end" signals the end of the PipelineCompilationJob, which carries the "compilationInfo", that contains the interesting bits of the OptimizedCompilationInfo, specifically whether the compile was successfull and which functions were inlined for example. This also adds two instant events "V8.AbortOptimization" and "V8.RetryOptimization" in "disabled-by-default-v8.compile" category that are emitted when TurboFan cannot optimize a certain function. In case of "V8.RetryOptimization", TurboFan might be able to optimize it later, whereas "V8.AbortOptimization" permanently disables the optimization of a given function. The JSON representation of this is ```js { "pid": 256639, "tid": 256639, "ts": 6935411377801, "tts": 159116, "ph": "I", "cat": "disabled-by-default-v8.compile", "name": "V8.AbortOptimization", "dur": 0, "tdur": 0, "args": { "reason": "Function is too big to be optimized", "function": { "id_ref": "0x600000001", "scope": "v8::internal::SharedFunctionInfo" } } }, ``` where the "function" refers to a previously emitted SNAPSHOT for the function in question. In the trace viewer it will show up as instant event under "v8.optimizingCompile.prepare" in case of the relevant example where optimization is disabled due to reaching the bytecode limit (as in the JSON above), i.e. it'll look something like this https://i.paste.pics/aafc2de9df10ea8f5acc1a761d80f07b.png for the example highlighted in the recent blog post https://ponyfoo.com/articles/javascript-performance-pitfalls-v8 that describes the optimization limit. The "v8.optimizingCompile.end" duration event will also carry this information as part of the "compilationInfo" object, but specifically for CI tools, etc. it might be a whole lot easier to just look for the "V8.AbortOptimization" instant event. Bug: v8:8598, v8:9039 Tbr: ulan@chromium.org Doc: bit.ly/v8-tracing-signals Change-Id: Ic87ac336004690c65b6b15ad73bc6fbd4b5f12c4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1511483 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#60448}
-
Sigurd Schneider authored
This reverts commit 6604f182. Bug: chromium:945341 Original change's description: > [heap] Clean-up keys of oldspace weakmaps during scavenge > > This CL adds handling for cleaning up weakmap (EphemeronHashTable) > keys during scavenge, even if the weakmap resides in oldspace. > > Change-Id: If8d711c050ddbcae4dd6e8da549e0c0d08ba47b2 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1523787 > Commit-Queue: Sigurd Schneider <sigurds@chromium.org> > Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > Cr-Commit-Position: refs/heads/master@{#60432} TBR=ulan@chromium.org,jarin@chromium.org,sigurds@chromium.org,leszeks@chromium.org Change-Id: I9dd9b11990a262a457fd1bedc2b45b4a786a81f7 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1538133Reviewed-by:
Sigurd Schneider <sigurds@chromium.org> Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#60447}
-
Milad Farazmand authored
Port 6604f182 Original Commit Message: This CL adds handling for cleaning up weakmap (EphemeronHashTable) keys during scavenge, even if the weakmap resides in oldspace. Change-Id: Idf8b6115e57b1229864afefe6ffee85acb5e7547 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1538320Reviewed-by:
Milad Farazmand <miladfar@ca.ibm.com> Reviewed-by:
Junliang Yan <jyan@ca.ibm.com> Commit-Queue: Milad Farazmand <miladfar@ca.ibm.com> Commit-Queue: Junliang Yan <jyan@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#60446}
-
Michael Starzinger authored
The target of a 'break' statement without a provided label must be a regular block belonging to a surrounding loop or switch statement, named blocks (i.e. the one that just define a label) on the other hand must be targeted specifically with the provided label (and not implicitly). This fixes the behavior by introducing a dedicated {BlockKind::kNamed} for this purpose. R=clemensh@chromium.org TEST=mjsunit/regress/regress-9022 BUG=v8:9022 Change-Id: I94c3d5b1196ed94b8b1b31f6eb3b68070cf324e8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1538126 Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by:Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#60445}
-
Sigurd Schneider authored
This reverts commit 660d8287. Reason for revert: breaks no-i18n build: https://ci.chromium.org/p/v8/builders/ci/V8%20Linux%20-%20noi18n%20-%20debug/25919 Original change's description: > [debug] Mark toLocaleString and TA#join builtins as side-effect free. > > Bug: chromium:940373 > Change-Id: If5f90ff5f873f0687c6a6a4063e0d09d6bbbd556 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1533157 > Reviewed-by: Yang Guo <yangguo@chromium.org> > Commit-Queue: Peter Wong <peter.wm.wong@gmail.com> > Cr-Commit-Position: refs/heads/master@{#60440} TBR=yangguo@chromium.org,peter.wm.wong@gmail.com,petermarshall@chromium.org,szuend@chromium.org Change-Id: I5ee52f8f37bea83e80c53838d232332cb3486640 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:940373 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1538132Reviewed-by:
-
Peter Marshall authored
The macros take implicit local arguments and make the tests harder to read. Remove the macros and add a helper to get size directly given this is the only use of the helper that returns the whole list. Remove the typedef of vector of trace events, because it is only used in two places now and is also called 'list' not vector. Use unique pointers for the ownership of MockTraceObject. Change-Id: Iec495c436cf7326224137321a84035c817622eaa Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1538131Reviewed-by:
-
Benedikt Meurer authored
The --type_info_threshold is no longer supported for a long time and doesn't do anything useful nowadays, so no point in having that around. Drive-by-fix: Remove the FeedbackVector::ComputeCounts() logic, since it's dead code anyways by now. Bug: v8:8834 Change-Id: I05f7517b3b82e34c0a83357337a456ab9c9f1f42 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1538128 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
-
Clemens Hammacher authored
{FrameArray} needs a way to keep {WasmCode} alive from a JS container. This CL instruces {GlobalWasmCodeRef}, which is the equivalent to a global handle: It increments the {WasmCode} reference counter on construction and decrements it on destruction. The {GlobalWasmCodeRef} is held in a {Managed} from JS. R=titzer@chromium.org Bug: v8:8217 Change-Id: I5604a666840c27078db63c8618412ca412525be1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1533862 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by:Ben Titzer <titzer@chromium.org> Cr-Commit-Position: refs/heads/master@{#60441}
-
peterwmwong authored
Bug: chromium:940373 Change-Id: If5f90ff5f873f0687c6a6a4063e0d09d6bbbd556 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1533157Reviewed-by:
Yang Guo <yangguo@chromium.org> Commit-Queue: Peter Wong <peter.wm.wong@gmail.com> Cr-Commit-Position: refs/heads/master@{#60440}
-
Joyee Cheung authored
It otherwise does not compile on macOS when V8_TRACE_FEEDBACK_UPDATES is enabled. Change-Id: Ie3abaf901a9e28a02aaebd1de96448ce097bd0d2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1537295Reviewed-by:
Igor Sheludko <ishell@chromium.org> Commit-Queue: Joyee Cheung <joyee@igalia.com> Cr-Commit-Position: refs/heads/master@{#60439}
-
Clemens Hammacher authored
This adds support to ref-count uses of WasmCode, and introduces a {WasmCodeRefScope} to be used whereever WasmCode objects need to be kept alive, e.g. because a pointer is passed around. Future CLs will introduce proper scopes in the whole code base and enable the DCHECK that's currently commented out. R=titzer@chromium.org Bug: v8:8217 Change-Id: I1659a0e9d57cd22fe70e6f2661d0d8af9f0906c7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1526005 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by: -
Jaroslav Sevcik authored
Bug: chromium:945187 Change-Id: I564a4495f13651ea9fdf1b95c25658b92ff9de49 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1538125Reviewed-by:
-
Benedikt Meurer authored
Before this change we had essentially two optimization limits, one hard limit in the TurboFan pipeline (128KiB), and a soft limit in the runtime profiler (60KiB). The hard limit was only relevant to --always-opt and other internal test infrastructure, and the soft limit was always enforced on regular JavaScript, but didn't properly disable further optimization for the function (so for example --trace-opt would continuesly report attempts to optimize the function). Now with this change we only have the hard limit, set to 60KiB, in the TurboFan pipeline and use that consistently. Bug: v8:8598 Change-Id: I9e2ae7cb67de4a2256d3a7b9c3aee3dab60c2ec1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1538127 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Jaroslav Sevcik <jarin@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
-
Sigurd Schneider authored
Change-Id: Ie09953d0b9453a1f22312ad1782e2c41b8230679 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1533858Reviewed-by:
-
Clemens Hammacher authored
Use the existing macros to load MemoryStart and MemorySize from the instance. R=titzer@chromium.org Change-Id: Iaa597fedcfc4581503d7cdf2fb94da6e285cc545 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1538122Reviewed-by:
-
Benedikt Meurer authored
This extends the existing PipelineStatistics in the TurboFan pipeline (also used for Wasm) to emit trace events for the various phases of the (optimized) compilation. This works for "disabled-by-default-v8.compile" and "disabled-by-default-v8.wasm" categories. We also rename the existing phase names to match the naming convention for the V8 trace events (starting with either "V8.TF" or "V8.Wasm") to make it easy to spot and categorize them in the trace viewer. This can be seen in action here https://i.paste.pics/a33c0e3942ff707af44f67ed4bac46b0.png taken from a run of Octane/TypeScript. Bug: v8:8598 Change-Id: Id40092ee8afc8d998532f8641780052769cad320 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1538121Reviewed-by:
-
Sigurd Schneider authored
This CL adds handling for cleaning up weakmap (EphemeronHashTable) keys during scavenge, even if the weakmap resides in oldspace. Change-Id: If8d711c050ddbcae4dd6e8da549e0c0d08ba47b2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1523787 Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
-
Clemens Hammacher authored
Both js-to-wasm-wrapper-cache-inl.h and wasm-import-wrapper-cache-inl.h do not include any inl headers, thus they can be plain headers. If they ever need to include inl headers again, we should split out the respective functions into a separete inl header to follow the usual pattern to have *both* a plain header *and* an inl header. R=mstarzinger@chromium.org Bug: v8:8834 Change-Id: I1b1b917a8e2c47f1354522479f8c57475bee6244 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1535826Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#60431}
-
Sigurd Schneider authored
Bug: v8:8557 Change-Id: I213b5944de72eb09a18e44789539b6b420e68068 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1538117Reviewed-by:
-
Michael Starzinger authored
R=hpayer@chromium.org BUG=v8:6792 Change-Id: I0e773a980b76b033e2561c37db1a43ab1b58da0b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1532071Reviewed-by:
Hannes Payer <hpayer@chromium.org> Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#60429}
-
Benedikt Meurer authored
Add tracing support for the %StackGuard() and %Interrupt() runtime calls and the individual actions performed in StackGuard::HandleInterrupts(). This includes: - "V8.GCHandleGCRequest" (in "disabled-by-default-v8.gc") when the GC_REQUEST bit is set. - "V8.WasmGrowSharedMemory" (in "disabled-by-default-v8.wasm") when the GROW_SHARED_MEMORY bit is set. - "V8.TerminateExecution" (in "v8.execute") when the TERMINATE_EXECUTION bit is set. - "V8.GCDeoptMarkedAllocationSites" (in "disabled-by-default-v8.gc") when the DEOPT_MARKED_ALLOCATION_SITES bit is set. - "V8.InstallOptimizedFunctions" (in "disabled-by-default-v8.compile") when the INSTALL_CODE bit is set. - "V8.InvokeApiInterruptCallbacks" (in "v8.execute") when the API_INTERRUPT bit is set. Now we also emit a trace event "V8.MarkCandidatesForOptimization" (in "disabled-by-default-v8.compile") in addition to the above from the RuntimeProfiler when we mark candidates for optimization at the end of each stack check. An example of the "V8.InstallOptimizedFunctions" in action (in the trace viewer) can be seen here: https://i.paste.pics/094a04af035eedc0690cd4079afa28f1.png This supersedes the previously introduced --trace-interrupts CLI flag, which is thus removed as part of this change. Bug: v8:8598 Change-Id: I3c3375d00b07cbe700b6912097d7264031ace802 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1538116 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/master@{#60428}
-
Andreas Haas authored
In the implementation of WebAssembly.compileStreaming and WebAssembly.instantiateStreaming, we did not handle the case where the input, which is a Promise, gets rejected. When this Promise got rejected, the Promise returned by compileStreaming remained pending forever. With this CL, the rejection object of the input Promise gets forwarded to the result Promise. I also extended the --wasm-test-streaming flag to provide WebAssembly.compileStreaming and WebAssembly.instantiateStreaming in d8. The difference to the Chrome versions of these function is that d8 does not know about Response objects. That's why in d8 compileStreaming and instantiateStreaming expect a Promise to an ArrayBuffer or a TypedArray and not to a Response object. Cq-Include-Trybots: luci.chromium.try:linux-blink-rel Bug: chromium:943487 Change-Id: I77f789e9ae5d50ae9c9bc92bf27dbfe338fe0f13 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1535817Reviewed-by:
-
Andreas Haas authored
R=mstarzinger@chromium.org Bug: v8:8834 Change-Id: If6bbd60e3d65abf78bb10911254e7fe24932831e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1538118Reviewed-by:
-
Clemens Hammacher authored
1) Pass {std::shared_ptr} by reference if a copy might not be needed. This applies both to accessors as well as constructing methods. This change often saves one atomic increment and decrement of the internal reference counter. 2) Use {std::make_shared} directly to improve memory management of the {std::shared_ptr}. This saves one dynamic memory allocation on all known implementations. R=titzer@chromium.org Bug: v8:8834 Change-Id: I1a951deb135082745885bc981662a8d6d6fb1a71 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1532333Reviewed-by: -
Allan Sandfeld Jensen authored
Change-Id: I3b9a85e53333349b30f3acb6219e7e47861ca042 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1491596Reviewed-by:
-
Mathias Bynens authored
Bug: v8:8834 Change-Id: Ie879ae77f0601682dcd17a61f3a18f49eb78fbee Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1535833 Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
-
Peter Marshall authored
This is used to convert files with binary proto data to the Trace Event .json format for use with the chrome://tracing viewer. Change-Id: Ib5478f6aa2326b5e085506859f4a7f30f95c79f5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1535823 Commit-Queue: Peter Marshall <petermarshall@chromium.org> Reviewed-by:
Mathias Bynens <mathias@chromium.org> Cr-Commit-Position: refs/heads/master@{#60422}
-
Benedikt Meurer authored
Inside V8 the TraceID class sits in v8::internal::tracing instead of trace_event_internal namespace (as in Chrome). Bug: v8:8834 Change-Id: I9464e6145c4fd4c794ac3f50052a5fa1b068aeed Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1535834 Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Peter Marshall <petermarshall@chromium.org> Reviewed-by:
-
Z Duong Nguyen-Huu authored
EmbedderDataArray, JSMessageObject, JSSet, JSMap, JSWeakSet, JSWeakMap Bug: v8:8952 Change-Id: I996d9e18006184b8ac7be7d362e8faf36e44aaef Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1534304Reviewed-by:
Simon Zünd <szuend@chromium.org> Commit-Queue: Z Nguyen-Huu <duongn@microsoft.com> Cr-Commit-Position: refs/heads/master@{#60420}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/724c206..625ee00 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/4b0dd1e..347c5e4 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/e4e1dde..ba35c7f Rolling v8/third_party/googletest/src: https://chromium.googlesource.com/external/github.com/google/googletest/+log/8b6d3f9..a18ac39 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/2e1c40d..ad70d89 TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: I9963ef2febd9ce74bdd0783822f8fe512b1d3977 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1537898Reviewed-by:
-
- 24 Mar, 2019 1 commit
-
-
Frank Tang authored
https://rawgit.com/fabalbon/proposal-intl-DateTimeFormat-formatRange/master/out/ Design Doc https://goo.gl/PGUQ1d Bug: v8:7729 Change-Id: I38b53ffdf610400b4132a25da99dac4be67bdf4b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1510574Reviewed-by:
-
