- 25 Mar, 2019 25 commits
-
-
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 <bmeurer@chromium.org> Commit-Queue: Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#60443}
-
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: Jaroslav Sevcik <jarin@chromium.org> Cr-Commit-Position: refs/heads/master@{#60442}
-
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: Ben Titzer <titzer@chromium.org> Cr-Commit-Position: refs/heads/master@{#60438}
-
Jaroslav Sevcik authored
Bug: chromium:945187 Change-Id: I564a4495f13651ea9fdf1b95c25658b92ff9de49 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1538125Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Jaroslav Sevcik <jarin@chromium.org> Cr-Commit-Position: refs/heads/master@{#60437}
-
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: Jaroslav Sevcik <jarin@chromium.org> Cr-Commit-Position: refs/heads/master@{#60436}
-
Sigurd Schneider authored
Change-Id: Ie09953d0b9453a1f22312ad1782e2c41b8230679 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1533858Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#60435}
-
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: Ben Titzer <titzer@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#60434}
-
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: Jaroslav Sevcik <jarin@chromium.org> Reviewed-by: Peter Marshall <petermarshall@chromium.org> Reviewed-by: Ben Titzer <titzer@chromium.org> Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#60433}
-
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: Jaroslav Sevcik <jarin@chromium.org> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#60432}
-
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: Jaroslav Sevcik <jarin@chromium.org> Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#60430}
-
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: Peter Marshall <petermarshall@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: Ben Titzer <titzer@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#60427}
-
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: Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#60426}
-
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: Ben Titzer <titzer@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#60425}
-
Allan Sandfeld Jensen authored
Change-Id: I3b9a85e53333349b30f3acb6219e7e47861ca042 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1491596Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Reviewed-by: Ben Titzer <titzer@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#60424}
-
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: Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#60423}
-
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: Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#60421}
-
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: 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@{#60419}
-
- 24 Mar, 2019 2 commits
-
-
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: Sathya Gunasekaran <gsathya@chromium.org> Commit-Queue: Frank Tang <ftang@chromium.org> Cr-Commit-Position: refs/heads/master@{#60418}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/c52372f..724c206 Rolling v8/buildtools: https://chromium.googlesource.com/chromium/src/buildtools/+log/735271f..31e0bb5 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/2f1832a..4b0dd1e Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/33bd582..e4e1dde Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/2116ee9..2e1c40d TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: Ie9b3b4889df9048f3bed1310dd05e852a6f98f45 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1536506Reviewed-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@{#60417}
-
- 22 Mar, 2019 13 commits
-
-
Sathya Gunasekaran authored
These flags are no longer necessary. Change-Id: Id686b2820ba05d7400cdb8ef9bb7f95c01cbe698 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1536451 Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org> Reviewed-by: Mathias Bynens <mathias@chromium.org> Cr-Commit-Position: refs/heads/master@{#60416}
-
Nico Weber authored
Remove a special case on mac hosts that was needed when is_clang wasn't the default on Win, but is unnecessary now and gets in the way. Bug: chromium:801780,chromium:495204 Change-Id: I8d6783c73e0c240704830a46304482e3ce94418b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1534634Reviewed-by: Adam Klein <adamk@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#60415}
-
Bill Budge authored
- Changes min and max sequences to propagate NaNs and signed zeroes. - Note that NaN propagation must preserve canonical NaNs. This is achieved by always returning canonical NaNs. This is also consistent with the WebAssembly scalar math spec. Bug: v8:8639 Change-Id: I04fdefabc54ea60f4d02e2081c32444a02dd6a83 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1524634 Commit-Queue: Bill Budge <bbudge@chromium.org> Reviewed-by: Deepti Gandluri <gdeepti@chromium.org> Cr-Commit-Position: refs/heads/master@{#60414}
-
Benedikt Meurer authored
The "V8.OptimizeCode" trace event (in "disabled-by-default-v8.compile" category) didn't include the setup of the OptimizedCompilationJob, which is quite expensive already and should be accounted for properly. Bug: v8:8598 Change-Id: Ieec139c8d555d02edfbc52e904ee214d1007afbd Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1533871Reviewed-by: Peter Marshall <petermarshall@chromium.org> Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#60413}
-
Santiago Aboy Solanes authored
Similar to x64's https://chromium-review.googlesource.com/c/v8/v8/+/1511486 Bug: v8:7703 Change-Id: Ifd634a36bb56a53cb9901d9dd0899b66229607ef Cq-Include-Trybots: luci.v8.try:v8_linux64_arm64_pointer_compression_rel_ng Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1535828 Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Auto-Submit: Santiago Aboy Solanes <solanes@chromium.org> Reviewed-by: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#60412}
-
Georg Neis authored
Process feedback and hints for Lda/StaNamed bytecodes w.r.t. access on the global proxy. This stores the property cells (or their absence) on the JSGlobalProxyData. Bug: v8:7790 Change-Id: Iadedea5494611c1b2ed38b6ce75687e084cc27f9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1499499 Commit-Queue: Jaroslav Sevcik <jarin@chromium.org> Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> Cr-Commit-Position: refs/heads/master@{#60411}
-
Milad Farazmand authored
Change-Id: I290ea07e4f6c66d04ee0daa04ac78a47d9f4432e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1535519Reviewed-by: Junliang Yan <jyan@ca.ibm.com> Reviewed-by: Milad Farazmand <miladfar@ca.ibm.com> Commit-Queue: Milad Farazmand <miladfar@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#60410}
-
Peter Marshall authored
We were hitting a DCHECK in WaitFor() when rel_time was negative. This was caused when GetNext() recalculated the wait time for a delayed task. In the first part of the loop we moved all delayed tasks which have passed their deadline into the immediate task queue. At the bottom of the loop we assume that all delayed tasks in the queue have a deadline in the future, but this isn't always the case as we use a new 'now' value for the calculation, and time could have elapsed. Fix this by using one 'now' value for an iteration of the loop. Bug: v8:9030 Change-Id: Ia49fb571f3c7c7d9f15c6a464ee0a9db814a7f03 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1535820 Commit-Queue: Peter Marshall <petermarshall@chromium.org> Reviewed-by: Hannes Payer <hpayer@chromium.org> Cr-Commit-Position: refs/heads/master@{#60409}
-
Sigurd Schneider authored
This is a reland of 1ca08865 Original change's description: > Reland "[regalloc] Introduce deferred fixed ranges" > > This is a reland of b1769313 > > Original change's description: > > [regalloc] Introduce deferred fixed ranges > > > > Fixed ranges are used to express register constraints in the > > allocator. This change splits these fixed ranges into one for > > normal code and deferred code. The former are handeled as before > > whereas the latter are only made visible while allocating > > registers for deferred code. > > > > This prevents forward looking decisions in normal code to be > > impacted by register constraints from deferred code. > > > > Change-Id: I67d562bb41166194e62765d5ab051bc961054fc7 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1477742 > > Commit-Queue: Sigurd Schneider <sigurds@chromium.org> > > Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> > > Reviewed-by: Sigurd Schneider <sigurds@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#60322} > > Change-Id: I1a31150256eb5608db985b144aab7ea457169d0d > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1530810 > Commit-Queue: Sigurd Schneider <sigurds@chromium.org> > Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> > Cr-Commit-Position: refs/heads/master@{#60364} Change-Id: If4a956716e7e4de132f706be2c395cdfdc04ec94 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1532328Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#60408}
-
Sven Sauleau authored
This CL changes the case of the variable name I introduced in a previous CL. Change-Id: I6d44eaf8361fa7e021c1107af49ce85238165449 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1535821Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Sven Sauleau <ssauleau@igalia.com> Cr-Commit-Position: refs/heads/master@{#60407}
-
Sigurd Schneider authored
Bug: v8:8834 Change-Id: Ifd5384fab1a1450275b0e8f193498b43dcbc3a5e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1532334Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#60406}
-
Sergiy Belozorov authored
TBR=sergiyb@chromium.org No-Try: true Bug: chromium:923304 Change-Id: I2f3cf3f314165a683d24cbf252d46bec6e5f011c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1535822 Commit-Queue: Sergiy Belozorov <sergiyb@chromium.org> Reviewed-by: Sergiy Belozorov <sergiyb@chromium.org> Cr-Commit-Position: refs/heads/master@{#60405}
-
Sven Sauleau authored
In the int64 lowering pass some parameter nodes are considered special and don't require any transformation. For instance the Wasm instance. With the experimental-wasm-bigint proposal, two new special parameters are going through the pass, this CL avoids transforming them. Change-Id: Ie99ffaff125b9ef8c56e1883aac9e18e4072fc3e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1532336 Auto-Submit: Sven Sauleau <ssauleau@igalia.com> Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Sven Sauleau <ssauleau@igalia.com> Cr-Commit-Position: refs/heads/master@{#60404}
-