- 05 Aug, 2020 7 commits
-
-
Zeynep Cankara authored
This CL aligns the timeline tracks by tracking the global start and end timestamps of both Map and IC events. Bug: v8:10644, v8:10735 Change-Id: Ib0ad086cdcb8ae3ae734df6480c5567f1f5125c9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2335183Reviewed-by:
Sathya Gunasekaran <gsathya@chromium.org> Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Commit-Queue: Zeynep Cankara <zcankara@google.com> Cr-Commit-Position: refs/heads/master@{#69242}
-
Almothana Athamneh authored
This CL ensures that we add the '--fuzzing' flag to the num_fuzzer script. Please note that NumFuzzer does not inherit the StandardTestRunner class but it inherits BaseTestRunner so we had to override _runner_flags. Bug: v8:10755 Change-Id: Ifb779ba402106b8f2ce4d0e13090ef2db468a6ae Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2335185 Commit-Queue: Almothana Athamneh <almuthanna@chromium.org> Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Reviewed-by:
Liviu Rau <liviurau@chromium.org> Cr-Commit-Position: refs/heads/master@{#69241}
-
Maya Lekova authored
Bug: chromium:1052746 Change-Id: I5c60625b25279866816a2f928e84d728b3f04d51 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2332157Reviewed-by:
Georg Neis <neis@chromium.org> Commit-Queue: Maya Lekova <mslekova@chromium.org> Cr-Commit-Position: refs/heads/master@{#69240}
-
Clemens Backes authored
Use the new jobs API for WebAssembly compilation. This avoids having to schedule as many background tasks as there are worker threads. Instead the one job specifies the maximum concurrency, which changes dynamically as new compile jobs become available. This also avoids the artificial deadline we used to ensure that other tasks get some share of the CPU resources if needed. Even though this CL moves actual wasm function completely over to the Jobs API, other similar tasks (like wrapper compilation) are still using the Task API and need to be ported in a follow-up CL. Also, we are still using the same priority for baseline compilation and tier up. We should split this in a follow-up CL to have two jobs with different priorities. This will also allow us to only block on baseline compilation where we currently block on both. R=ahaas@chromium.org CC=gab@chromium.org Bug: chromium:1101340 Change-Id: I5656697753346e5fdb15d578425cdb949ac6e364 Cq-Include-Trybots: luci.v8.try:v8_linux64_tsan_rel_ng Cq-Include-Trybots: luci.v8.try:v8_linux64_tsan_isolates_rel_ng Cq-Include-Trybots: luci.chromium.try:linux-rel Cq-Include-Trybots: luci.v8.try:v8_linux_blink_rel Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2280100 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by:
Andreas Haas <ahaas@chromium.org> Reviewed-by:
Thibaud Michaud <thibaudm@chromium.org> Cr-Commit-Position: refs/heads/master@{#69239}
-
Zeynep Cankara authored
This CL initialises the change theme button in correct place and adds the functionality to change theme after the data load. Bug: v8:10644 Change-Id: I7397933ff9d12a2ac270d025df1b3327801d89be Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2336800Reviewed-by:
-
Martin Bidlingmaier authored
R=jgruber@chromium.org Bug: v8:10765 Change-Id: Iae389bd129784c08287dec7c4cb8ebeaa6a6120c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2336794 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#69237}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/b2c431c..2e78142 Rolling v8/buildtools: https://chromium.googlesource.com/chromium/src/buildtools/+log/6139217..1ecfe3c Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/ce6a663..ac60992 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/6c7b829..486f181 Rolling v8/third_party/zlib: https://chromium.googlesource.com/chromium/src/third_party/zlib/+log/a21a4e8..7492de9 TBR=machenbach@chromium.org,tmrts@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I20f8da749d85439c36f09fe1cc30254094601e9e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2337006Reviewed-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@{#69236}
-
- 04 Aug, 2020 25 commits
-
-
Tamer Tas authored
fuzzer testsuite tests are not run due to a missing subclass method '_should_filter_by_name' in fuzzer/testcfg.py This CL fixes the filtering for the 'fuzzer' testsuite R=machenbach@chromium.org Bug: v8:10770 Change-Id: I9a4b0e0c6c79f4b525ee284df343acccc965f732 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2336802 Auto-Submit: Tamer Tas <tmrts@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by:
-
Milad Farazmand authored
As this is a unary operation src operands must be the same. Change-Id: Id6e3b11fdb942596c05c38591379e6d9fd71f19e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2332865Reviewed-by:
Junliang Yan <jyan@ca.ibm.com> Commit-Queue: Milad Farazmand <miladfar@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#69234}
-
Ng Zhi An authored
This test uses a i64x2.shr_s to shift a v128 with all bits set by 1, resulting in v128 with all bits set (no change). This value is then dropped, and param[2] (3), is returned. Without the fix, -1 is returned, since i64x2.shr_s overwrites the register for param[2] with 0xffffffff. Bug: v8:10752 Bug: chromium:1111522 Change-Id: I0310bf6039be780a6738689069cdbcfa3a24bbdb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2335779 Commit-Queue: Zhi An Ng <zhin@chromium.org> Reviewed-by:
Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#69233}
-
Milad Farazmand authored
We can use r0 itself without the need of loading it with "0", if it is used as the first input of MemOperand. Change-Id: I71aafea8bba098f925c55eb9127c6b37ac37cb7b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2332864 Commit-Queue: Milad Farazmand <miladfar@ca.ibm.com> Reviewed-by:
-
Ng Zhi An authored
Swizzles are shuffles that only use values from 1 operand, e.g. v8x16.shuffle 0 1 2 3 0 0 0 0 4 5 6 7 0 0 0 0 (all the values are < 16). Match such patterns and emit an optimized codegen that uses less registers and instructions. Only implemented for x64 for now, the other backends will come in follow-up patches. Bug: v8:10696 Change-Id: Iffa694b04c97313eab7d138e4bdad7c0c85cda89 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2335419Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
Bill Budge <bbudge@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#69231}
-
Shu-yu Guo authored
Bug: chromium:1112221 Change-Id: I402df2071eed82f44669910cf8e234f727e09581 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2335549Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Commit-Queue: Shu-yu Guo <syg@chromium.org> Cr-Commit-Position: refs/heads/master@{#69230}
-
Mythri A authored
Change-Id: I0117b0c2b646cb1005b63e9648d604b26581d977 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2335187Reviewed-by:
-
Dominik Inführ authored
Add safepoints to GC methods in Heap. There is still stuff in Heap::CollectGarbage which might work better or more precise in a global safepoint. Be conservative here and move everything into the safepoint, eventually we can start to move code out that is fine to run outside the safepoint. Bug: v8:10315 Change-Id: I656dfd72f032eff6f386cec63a02777506650aa7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2335192 Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#69228}
-
Milad Farazmand authored
Change-Id: Ie2668026c5b55af8813f159277bdbc83116c1a00 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2336776Reviewed-by:
-
Ross McIlroy authored
Only expose top-level functions for DefineOutputs and AllocateRegisters in the mid-tier register allocator, rather than exposing the MidTierRegisterAllocator object, to be in-line with AllocateSpillSlots and PopulateReferenceMaps. BUG=v8:9684 Change-Id: I93dcff77f5e50dab9b373b4415029361078d58e1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2323361 Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Reviewed-by:
-
Dominik Inführ authored
This ensures that large object has exactly the size of a regular page. Avoids wasting memory due to alignment. Bug: v8:10315 Change-Id: Ife8051313f1ea8c1fc0ba0afcc4e5db11f27adca Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2335191Reviewed-by:
-
Dominik Inführ authored
LocalAllocationBuffer is used on the background thread so it needs to use CreateFillerObjectAtBackground for creating filler objects. Bug: v8:10315 Change-Id: Ifc22d87e1e835cfdd65d82fc79b20ee74b2c87b1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2336795Reviewed-by:
-
Kim-Anh Tran authored
This adds CDP methods to support skipping locations on stepOver and stepInto. Bug: chromium:1105765 Change-Id: I8b902009883807082cf5fda0411b992e90dee81d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2335181Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
Hannes Payer <hpayer@chromium.org> Commit-Queue: Kim-Anh Tran <kimanh@chromium.org> Cr-Commit-Position: refs/heads/master@{#69223}
-
Zeynep Cankara authored
Add functionality to emit an event upon double clicking on an event type on the timeline track selected entries panel. Bug: v8:10644 Change-Id: I54d4397abfeab471f01c2b24bae4eb1ff705afcd Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2328787Reviewed-by:
-
Dan Elphick authored
Test now passes even if RO_SPACE sharing is enabled. Bug: v8:10454 Change-Id: Ic7377c3367199383bb6a96a9beedcc52bbc3362f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2335184 Commit-Queue: Dan Elphick <delphick@chromium.org> Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Auto-Submit: Dan Elphick <delphick@chromium.org> Reviewed-by:
-
Manos Koukoutos authored
Changes: - Fix error message typo in function-body-decoder. - Generalize wasm test macros related to reference types. - Change wasm-gc test API to return bytes. - Add unittests for ref.test/cast. Bug: v8:7748 Change-Id: I361987e0b6ac90c4e89a49a8abc125757a5fc8d0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2317319 Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Reviewed-by:
-
Georg Neis authored
This was wrong because ObjectBoilerplateDescription is a subclass of FixedArray. The wrong order didn't cause problems because we explicitly call the ObjectBoilerplateDescription constructor in the places that matter. Bug: v8:7790 Change-Id: I63b6b8741472862d2b1b9b843d7aa2490c620f87 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2335180 Commit-Queue: Georg Neis <neis@chromium.org> Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org> Reviewed-by:
Santiago Aboy Solanes <solanes@chromium.org> Auto-Submit: Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#69219}
-
Zeynep Cankara authored
This CL aims to clean the code in App Class to handle State, View according to the Model-View-Controller design pattern. Bug: v8:10644, v8:10735 Link: https://docs.google.com/presentation/d/1ssCIWKS5TIp_PHZRUx2BfElEz6JFrYzz_Ce1h1g8ZBg/edit?usp=sharing Change-Id: Ie36d437df0df574f505a4396b26526a82215f237 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2324247 Commit-Queue: Zeynep Cankara <zcankara@google.com> Reviewed-by:
-
Dominik Inführ authored
Let StressConcurrentAllocatorTask allocate small, medium and large objects to test different code paths. Bug: v8:10315 Change-Id: Ifff7e91bc95f0d926a58321b481183e9acf8bd32 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2335182 Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Reviewed-by:
-
Dominik Inführ authored
This is a reland of b354e344 This CL adds 3 fixes: * Unprotect code object before creating filler * Allows AllocationObserver::Step to add more AllocationObservers * Update limit in NewSpace::UpdateLinearAllocationArea Original change's description: > [heap] Refactor allocation observer in AllocationCounter > > Moves accounting of allocation observers into the AllocationCounter > class. This CL removes top_on_previous_step_ for counters that are > increased regularly in the slow path of the allocation functions. > > AdvanceAllocationObservers() informs the AllocationCounter about > allocated bytes, InvokeAllocationObservers() needs to be invoked when > an allocation step is reached. NextBytes() returns the number of bytes > until the next AllocationObserver::Step needs to run. > > Bug: v8:10315 > Change-Id: I8b6eb8719ab032d44ee0614d2a0f2645bfce9df6 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2320650 > Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > Cr-Commit-Position: refs/heads/master@{#69170} Bug: v8:10315 Change-Id: I89ab4d5069a234a293471f613dab16b47d8fff89 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2332805Reviewed-by:
-
Clemens Backes authored
A minor refactoring to the logic for triggering callbacks: 1. If compilation failed, do only trigger the kFailedCompilation event. 2. Use the TriggerCallbacks method also for triggering the kFailedCompilation event. R=thibaudm@chromium.org Bug: chromium:1101340 Change-Id: I3446d708d28068448e6eca3e637c9af673f5311d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2332171Reviewed-by:
-
evih authored
Bug: v8:10701 Change-Id: I6e6d0c67889f29647ea225163cf051d3432da338 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2335058Reviewed-by:
-
Jakob Gruber authored
In preparation for adding new NCI (and TP) code kinds. - Free the unused bit in Code::flags. - Be more precise about the flag field sizes (int32 instead of int). - Add and refactor related static asserts. Bug: v8:8888 Change-Id: Ice0d4df9de528de77dfb5c04279cfdc4b030efc9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2328788 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
Nico Hartmann <nicohartmann@chromium.org> Cr-Commit-Position: refs/heads/master@{#69213}
-
Benedikt Meurer authored
The DevTools front-end uses so-called Wasm evaluator modules to get to the values of variables in scope when the wasmDWARFDebugging experiment is turned on. We rely on the `Debugger.executeWasmEvaluator()` method in the Chrome DevTools Protocol (CDP) to accomplish this, which in turn is controlled by this global flag. Since we intend to gather more feedback from selected internal / external teams on the DWARF debugging experience, we need to ship this flag by default to make it easier to test the new experiment without having to fiddle with additional flags to pass to Chrome on the command line (and asking folks whether they really started Chrome correctly). Bug: chromium:1041362 Change-Id: I1e170383fa7a34c41eec8c4867c38b7d8e871e8b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2335072 Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
Michael Hablich <hablich@chromium.org> Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#69212}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/edf75c7..b2c431c Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/f80ffe3..ce6a663 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/98b332f..6c7b829 TBR=machenbach@chromium.org,tmrts@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: If97b9c9eb4d56364f94f9e0453ba67b462643505 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2335955Reviewed-by:
-
- 03 Aug, 2020 8 commits
-
-
Dirk Pranke authored
I tripped over this str/bytes issue as part of bringing up the Chromium build under Python3. Bug: chromium:1112471 Change-Id: I723c7d9df8bcac24c160c549a03dcbd34c1d92f6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2334222 Commit-Queue: Dirk Pranke <dpranke@google.com> Reviewed-by:
Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/master@{#69210}
-
Michael Achenbach authored
No-Try: true Change-Id: If5ed824ad3ea1a2815a0a48ed2668281733ac533 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2332603Reviewed-by:
Zhi An Ng <zhin@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Auto-Submit: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#69209}
-
Ng Zhi An authored
x64's implementation of i64x2.shr_s was overwriting the scratch register. kScratchRegister is used to hold the extracted lane of the SIMD register, but in certain cases [0], is also used to back up the value of rcx. When this happens, the supposed backed-up rcx was overwritten (definitely) by each extract lane, so we end up restoring an incorrect value of rcx, leading to an eventual crash in certain benchmarks, when this extracted lane was used as a memory operand (see linked bugs). [0] when register holding the shift value is not rcx, which sarq_cl relies on Bug: v8:10752 Bug: chromium:1111522 Change-Id: Iaf3264e16f94e78bad4290783757f0b722d40411 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2334354Reviewed-by:
-
Jakob Kummerow authored
This is a stop-gap solution (while we wait for a proper spec) that lets managed WasmGC objects perform round-trips through JavaScript. On the JavaScript side, they appear as empty/opaque. Bug: v8:7748 Change-Id: I0dd368bc14d622f3ef41871484228267359e9b5b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2316306 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/master@{#69207}
-
Shu-yu Guo authored
This reached consensus in the July 2020 TC39: https://github.com/tc39/ecma262/pull/2054 Bug: v8:10769 Change-Id: Iecea1d9d9c9be5c2fbfb820aed2285719c4e6382 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2333350 Commit-Queue: Shu-yu Guo <syg@chromium.org> Reviewed-by:
Marja Hölttä <marja@chromium.org> Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/7c2575f..edf75c7 Rolling v8/buildtools: https://chromium.googlesource.com/chromium/src/buildtools/+log/42e9461..6139217 TBR=machenbach@chromium.org,tmrts@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I80cf25941086ec9e94f0f5806c8c550ea0210280 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2334660Reviewed-by:
-
Clemens Backes authored
After allocating a new code space, we do some initial allocations in the new space (e.g. for the jump table). These allocations are not allowed to fail. If this in indeed what's happening in the linked bug, this CHECK will give fuzzers a chance to find us a reproducer. Drive-by: Introduce {WasmCodeAllocator::kUnrestrictedRegion} to remove magic constants. R=ahaas@chromium.org Bug: v8:1111266 Change-Id: Ia76721653226bd4aa346b89ffab0c80f67892794 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2333250 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by: -
Marja Hölttä authored
If we cancel the task in the thread where it's supposed to run, task cancelling will always succeed. This simplifies the logic. Bug: v8:10239 Change-Id: I3fb5c93a49c52d958aa947d693700161bc18eee5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2332807Reviewed-by:
-
