- 29 Jan, 2018 13 commits
-
-
Michael Achenbach authored
This adds back an option for interrupt budget available in no-snap builds. This also adds a fuzzer configuration for numfuzz that enables fuzzing the interrupt budget option. A new flag --disable-analysis allows to generally skip the fuzzer's analysis phase, which can be chosen for interrupt budget, which doesn't support an analysis phase. Bug: v8:6917 Change-Id: I546dd9ee41c3e0fb027108ef4606a34514f230d4 Reviewed-on: https://chromium-review.googlesource.com/885805Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Reviewed-by:
Yang Guo <yangguo@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#50929}
-
Gabriel Charette authored
This reverts commit 8a27c7d3. Reason for revert: Having more tasks then work items is intentional in some use cases, i.e. Scavenging where RunInParallel() does parallel processing on a dynamic workload *after* the initial set of work items: { barrier_->Start(); TimedScope scope(&scavenging_time); PageScavengingItem* item = nullptr; while ((item = GetItem<PageScavengingItem>()) != nullptr) { item->Process(scavenger_); item->MarkFinished(); } do { scavenger_->Process(barrier_); } while (!barrier_->Wait()); scavenger_->Process(); } Original change's description: > v8::ItemParallelJob : Do not launch more Tasks than there are Items to process. > > Except when there are 0 items. For some reason I don't quite understand yet, not > calling Run() on tasks_[0] when there are 0 items results in DCHECKs... > > Bug: chromium:806237 > Change-Id: I38c8fffde64a42f93f4efda492832651137eebd7 > Reviewed-on: https://chromium-review.googlesource.com/888704 > Commit-Queue: Gabriel Charette <gab@chromium.org> > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Cr-Commit-Position: refs/heads/master@{#50924} TBR=gab@chromium.org,mlippautz@chromium.org Change-Id: Iad2ab16bb41f339de8e3fbca1c08c5d26b8a0111 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:806237 Reviewed-on: https://chromium-review.googlesource.com/891186Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Gabriel Charette <gab@chromium.org> Cr-Commit-Position: refs/heads/master@{#50928}
-
Michael Achenbach authored
This is the first step for retiring swarming tests with gyp. TBR=sergiyb@chromium.org NOTRY=true Bug: v8:7335 Change-Id: I98145843b91d47a77e06173c2a421fcc0d4e5586 Reviewed-on: https://chromium-review.googlesource.com/891230 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by:
-
Michael Starzinger authored
R=tebbi@chromium.org Change-Id: Iae9a3774eb7913388350ce3cd0a96d6a6cca25e8 Reviewed-on: https://chromium-review.googlesource.com/885845Reviewed-by:
Tobias Tebbi <tebbi@chromium.org> Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#50926}
-
Ross McIlroy authored
BUG=chromium:798964 Change-Id: I63c373ef3f27a3295fc79f5c82d78b5fd89a83da Reviewed-on: https://chromium-review.googlesource.com/888752 Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#50925}
-
Gabriel Charette authored
Except when there are 0 items. For some reason I don't quite understand yet, not calling Run() on tasks_[0] when there are 0 items results in DCHECKs... Bug: chromium:806237 Change-Id: I38c8fffde64a42f93f4efda492832651137eebd7 Reviewed-on: https://chromium-review.googlesource.com/888704 Commit-Queue: Gabriel Charette <gab@chromium.org> Reviewed-by:
-
Leszek Swirski authored
Wide suspends have a "wide" (or "extra-wide") bytecode at their offset, rather than the suspend itself, so they were failing the return check. Bug: chromium:805765 Change-Id: Iabfc2a2167d09eda2f6885d9100287aadcd8fee9 Reviewed-on: https://chromium-review.googlesource.com/887082Reviewed-by:
-
Leszek Swirski authored
Bug: chromium:806200 Change-Id: If76a8cb5b988321d38d170dfba7c1fc5354e2667 Reviewed-on: https://chromium-review.googlesource.com/888922Reviewed-by:
Adam Klein <adamk@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/master@{#50922}
-
Daniel Clifford authored
There is currently no test that shows this bug (it was found as part of the DSL experiment), but it should get fixed anyway and it will eventually be verified by the A.p.splice CSA builtin port that is in progress. Change-Id: I9b6da8dc8f3151ad0b0a06c3ca10d604060efef7 Reviewed-on: https://chromium-review.googlesource.com/890580Reviewed-by:
Igor Sheludko <ishell@chromium.org> Commit-Queue: Daniel Clifford <danno@chromium.org> Cr-Commit-Position: refs/heads/master@{#50921}
-
Daniel Clifford authored
This makes the ArrayBuiltinsAssembler consistent with the StringBuiltinsAssembler and paves the way for tools that expect the assemblers to have a common structure. Change-Id: I7470fc2cf144f9cc2fdbcee99b31daed267550be Reviewed-on: https://chromium-review.googlesource.com/889933Reviewed-by:
Michael Stanton <mvstanton@chromium.org> Commit-Queue: Daniel Clifford <danno@chromium.org> Cr-Commit-Position: refs/heads/master@{#50920}
-
Jaroslav Sevcik authored
Bug: v8:5267 Change-Id: I649554733fdbd00c8e82b09aca35b0ff1f823560 Reviewed-on: https://chromium-review.googlesource.com/890262Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Jaroslav Sevcik <jarin@chromium.org> Cr-Commit-Position: refs/heads/master@{#50919}
-
Yang Guo authored
R=machenbach@chromium.org Bug: v8:7335 Change-Id: Ic89f9cd1fd45ece80da24c85559ef04bee93ee64 Reviewed-on: https://chromium-review.googlesource.com/888699 Commit-Queue: Yang Guo <yangguo@chromium.org> Reviewed-by:
-
Michael Achenbach authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/4ab66b7..8bf670e Rolling v8/buildtools: https://chromium.googlesource.com/chromium/buildtools/+log/437a616..f115f47 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/8d63750..82f653f TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: Ia2422b93bffa423b4452037ecc27b1f69c14a764 Reviewed-on: https://chromium-review.googlesource.com/890367Reviewed-by:
v8 autoroll <v8-autoroll@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#50917}
-
- 27 Jan, 2018 3 commits
-
-
Michael Achenbach authored
TBR=sergiyb@chromium.org NOTRY=true Bug: chromium:786303 Change-Id: Ia88c6c6e69f7c96dc1ac6d4b4ab140a06711f0f1 Reviewed-on: https://chromium-review.googlesource.com/890520 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by:
-
Michael Achenbach authored
Without realm-eval, the toplevel references in loaded tests are not garbage-collected and changes in the tests can affect the global object. TBR=ulan@chromium.org NOTRY=true Bug: v8:7379, v8:7376 Change-Id: Id4d451e38fe49c6531a07d541ad3c67298b6acf2 Reviewed-on: https://chromium-review.googlesource.com/890519 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by:
-
Jungshik Shin authored
Bug: chromium:801602 Test: intl/date-format/month-far-future.js Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng Change-Id: Ie2279680e8879c943cbf0873a933d2633e759212 Reviewed-on: https://chromium-review.googlesource.com/868376Reviewed-by:
-
- 26 Jan, 2018 24 commits
-
-
Sathya Gunasekaran authored
import() is shipping by default in Chrome 63 and import.meta is shipping in Chrome 64 already. The flag still exists so that embedders can turn off the feature if required. Bug: v8:5785, v8:6693 Change-Id: Ie6c8f90927958022900f677ea5a771527111aece Reviewed-on: https://chromium-review.googlesource.com/889658 Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org> Reviewed-by:
-
Michael Achenbach authored
This reverts commit 4dcf68e9. Reason for revert: Bug should be fixed. Original change's description: > [test] Skip tests failing on gc fuzzer > > Temporarily skipping tests until a fix has landed. > > TBR=ofrobots@google.com > NOTRY=true > > Bug: v8:7313 > Change-Id: I9d55f1ba190ee8104b90fd80c4b1de05508475e5 > Reviewed-on: https://chromium-review.googlesource.com/888642 > Commit-Queue: Michael Achenbach <machenbach@chromium.org> > Reviewed-by: Michael Achenbach <machenbach@chromium.org> > Cr-Commit-Position: refs/heads/master@{#50900} TBR=machenbach@chromium.org,ofrobots@google.com,majeski@google.com Change-Id: I9ac4800331f572e23c24d936f8b6c51884beeacb No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:7313 Reviewed-on: https://chromium-review.googlesource.com/888563Reviewed-by:
-
Jakob Kummerow authored
Bug: v8:7369 Change-Id: I35b69295a4f9ffab0d5d0501f2f0252dee1a48a3 Reviewed-on: https://chromium-review.googlesource.com/887428 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#50911}
-
Ali Ijaz Sheikh authored
These assertions would have caught the bug closer to the source. BUG=v8:7313 Change-Id: I19b75c3fc7bff8216dda370114ff00326f128116 Reviewed-on: https://chromium-review.googlesource.com/887175Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Ali Ijaz Sheikh <ofrobots@google.com> Cr-Commit-Position: refs/heads/master@{#50910}
-
Ali Ijaz Sheikh authored
Don't start new steps recursively if a step is already in progress. Having this property on a space is not sufficient, as an allocation is a global (heap-wide) event. Computing the next step size, for example is a property of all observers in existence rather than the spaces in existence. In this case a failure was due to the fact that we attempted to compute the next step size while a given observer was mid-way through its step triggered from a different space. bytes_to_next_step_ was partially updated at that point. BUG=v8:7313 Change-Id: Iaf632fce2cfd5ed49b0f41a69c3694e505e17d81 Reviewed-on: https://chromium-review.googlesource.com/887174 Commit-Queue: Ali Ijaz Sheikh <ofrobots@google.com> Reviewed-by:
-
Michael Lippautz authored
Tbr: ulan@chromium.org No-try: true Bug: v8:7266 Change-Id: Ia0965fa085d8d92b65a9353174e123337dc1ef6b Reviewed-on: https://chromium-review.googlesource.com/888585Reviewed-by:
-
Clemens Hammacher authored
This ensures that i32 values which are loaded into 64 bit registers have the upper 32 bits cleared. R=titzer@chromium.org Bug: v8:6600 Change-Id: I5eb2b65ac079b5683c83d755b1aa4a626411d5d4 Reviewed-on: https://chromium-review.googlesource.com/888702Reviewed-by:
Ben Titzer <titzer@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#50907}
-
Georgia Kouveli authored
Use a sequence of move instructions instead. Bug: Change-Id: I63a45ce7baaa9ebcba0d3e86910839e2ddedecd5 Reviewed-on: https://chromium-review.googlesource.com/888561Reviewed-by:
-
Michael Achenbach authored
TBR=sergiyb@chromium.org Bug: v8:7343 Change-Id: I0739a72f6453d682eb840b1b3650fc697c05df7d Reviewed-on: https://chromium-review.googlesource.com/888643Reviewed-by:
-
Sigurd Schneider authored
This CL uses UTF16 encoding internally in the string iterator, thereby saving a few shifts, ors, and ands. Bug: v8:7270 Change-Id: I3ac9e0e8c4b64eb1d6c796597eb0b3413c5f516b Reviewed-on: https://chromium-review.googlesource.com/887085Reviewed-by:
Jaroslav Sevcik <jarin@chromium.org> Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#50904}
-
Michal Majewski authored
They have been replaced with num_fuzzer. Bug: v8:6917 Change-Id: I2f78df308cec0a58f0d665bce82503dee68fcebc Reviewed-on: https://chromium-review.googlesource.com/888641Reviewed-by:
-
Ivica Bogosavljevic authored
Port 1abeb5a3 Change-Id: Ib31abb7e5e920b319d0e485bf5bcc29fdc018bbc Bug: chromium:806078 Reviewed-on: https://chromium-review.googlesource.com/888744Reviewed-by:
Miran Karić <miran.karic@mips.com> Commit-Queue: Ivica Bogosavljevic <ivica.bogosavljevic@mips.com> Cr-Commit-Position: refs/heads/master@{#50902}
-
Michal Majewski authored
This is a reland of 8f4407fb. Original change's description: > [test] Keep the order of variants > > Bug: v8:6917 > Change-Id: I7e04255649f62a28f0ed07ccb4fbaf4825498bf6 > Reviewed-on: https://chromium-review.googlesource.com/886841 > Commit-Queue: Michał Majewski <majeski@google.com> > Reviewed-by: Michael Achenbach <machenbach@chromium.org> > Cr-Commit-Position: refs/heads/master@{#50874} Bug: v8:6917 Change-Id: I9d4c617ccec6db8929af3095f2f27d8964c5d6b8 Reviewed-on: https://chromium-review.googlesource.com/888582Reviewed-by:
-
Michael Achenbach authored
Temporarily skipping tests until a fix has landed. TBR=ofrobots@google.com NOTRY=true Bug: v8:7313 Change-Id: I9d55f1ba190ee8104b90fd80c4b1de05508475e5 Reviewed-on: https://chromium-review.googlesource.com/888642 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by:
-
Ross McIlroy authored
Refactors bytecode register access to avoid having to deal with register indexes directly. - Changes Load/StoreRegister to Load/StoreRegisterAtOperandIndex - Adds RegisterList abstraction for dealin with lists of registers - Adds helpers for Loading / Storing register pairs / triples. Change-Id: I34427e4bd7314dce0230572212580d6a93ccc2d4 Reviewed-on: https://chromium-review.googlesource.com/887062Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#50899}
-
Michael Starzinger authored
R=jarin@chromium.org BUG=v8:6409 Change-Id: I7d9d6a2d1f000ff4ef3bb543bc2fe8705ff21363 Reviewed-on: https://chromium-review.googlesource.com/889098Reviewed-by:
-
Ulan Degenbaev authored
Bug: chromium:802300 Change-Id: I187f72eda80ae7d6a705361bdd36e79196f51293 Reviewed-on: https://chromium-review.googlesource.com/888743 Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
-
Ulan Degenbaev authored
Passing --trace_duplicate_threshold_kb=XX will print stats about duplicates on the heap in Heap::CollectAllAvailableGarbage function. One way to trigger the tracing is to force GC in DevTools. Change-Id: I535ae202c796c3dcf7262a0d0bfd2702f44ac27a Reviewed-on: https://chromium-review.googlesource.com/888746Reviewed-by:
-
Michael Achenbach authored
This reverts commit 8f4407fb. Reason for revert: Failing in old test runner. See comment. Original change's description: > [test] Keep the order of variants > > Bug: v8:6917 > Change-Id: I7e04255649f62a28f0ed07ccb4fbaf4825498bf6 > Reviewed-on: https://chromium-review.googlesource.com/886841 > Commit-Queue: Michał Majewski <majeski@google.com> > Reviewed-by: Michael Achenbach <machenbach@chromium.org> > Cr-Commit-Position: refs/heads/master@{#50874} TBR=machenbach@chromium.org,sergiyb@chromium.org,majeski@google.com Change-Id: Ia8608053e080c70d2ac09d7921a6abb6cd0e338f No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:6917 Reviewed-on: https://chromium-review.googlesource.com/888749Reviewed-by:
-
Michael Achenbach authored
This reverts commit f4ebbb3f. Reason for revert: Suspected to make things worse than better, e.g.: https://chromium-swarm.appspot.com/task?id=3b4b2f864304f010&refresh=10&show_raw=1 and https://chromium-swarm.appspot.com/task?id=3b4b2f8045da5510&refresh=10&show_raw=1 Original change's description: > [test] Let fuzzer total timeout also stop the execution loop > > TBR=sergiyb@chromium.org > > Bug: v8:6917 > Change-Id: I5bc8f49dc01d98949e3efab01192c663de8027bf > Reviewed-on: https://chromium-review.googlesource.com/888578 > Commit-Queue: Michael Achenbach <machenbach@chromium.org> > Reviewed-by: Michael Achenbach <machenbach@chromium.org> > Cr-Commit-Position: refs/heads/master@{#50887} TBR=machenbach@chromium.org,sergiyb@chromium.org,majeski@google.com Change-Id: Ib9f530348594e361d491e827aa03a38f41da9f1a No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:6917 Reviewed-on: https://chromium-review.googlesource.com/888519Reviewed-by:
-
Michael Lippautz authored
Bug: v8:7266 Change-Id: I2193d762d0f59b061be79bb3bbd280520728185a Reviewed-on: https://chromium-review.googlesource.com/888622Reviewed-by:
-
Michael Lippautz authored
Tbr: ulan@chromium.org No-try: true Bug: v8:7266 Change-Id: I84195b61d3f47cf2152cf68c2dc17a391c7ffec7 Reviewed-on: https://chromium-review.googlesource.com/889058Reviewed-by:
-
Yang Guo authored
This file is no longer used by our Node.js branch, as it has been updated to use gypfiles/v8.gyp. R=machenbach@chromium.org Bug: v8:7335 Change-Id: I6fe67b0839f2d7f4e2ec2df70f6cd88f25af7d92 Reviewed-on: https://chromium-review.googlesource.com/888745Reviewed-by:
-
Igor Sheludko authored
Do not overwrite handle values in AddNamedProperty which could cause invalid handles in combination with CanonicalHandleScope. Bug: chromium:802333 Change-Id: I373ab60579901bba65336ae3814e466e07392e22 Reviewed-on: https://chromium-review.googlesource.com/873032Reviewed-by:
-
