- 24 Apr, 2019 2 commits
-
-
v8-ci-autoroll-builder authored
Rolling v8/test/wasm-js/data: https://chromium.googlesource.com/external/github.com/WebAssembly/spec/+log/c46d4fa..43898ad [spec] Fix off-by-one error in table grow size limit (#1005) (Andreas Rossberg) https://chromium.googlesource.com/external/github.com/WebAssembly/spec/+/43898ad TBR=ahaas@chromium.org,clemensh@chromium.org Change-Id: Ibfc45cc4f5bc81e72c3340d830f059b5493f069e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1581082Reviewed-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@{#60961}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/7dae72d..5160e91 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/fb33e51..429d9b4 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/6d9913a..0d82718 Rolling v8/third_party/googletest/src: https://chromium.googlesource.com/external/github.com/google/googletest/+log/9f893b9..a53e931 TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: Ic65275bf40a1d69ef176c24b3cf75f7de5d84085 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1580800Reviewed-by:
-
- 23 Apr, 2019 24 commits
-
-
Z Duong Nguyen-Huu authored
Bug: chromium:953888 Change-Id: If2aa613bac18e61ac733102b45b0ebb6553eae1a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1579539Reviewed-by:
Igor Sheludko <ishell@chromium.org> Commit-Queue: Z Nguyen-Huu <duongn@microsoft.com> Cr-Commit-Position: refs/heads/master@{#60959}
-
Michael Achenbach authored
Change-Id: I574f647245d215b03a59b6c3dd6889e94f4d7708 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1578507Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#60958}
-
Sathya Gunasekaran authored
In the PerformPromise{All, Race, AllSettled} operations, the resolve property of the constructor is looked up only once. In the implementation, for the fast path, where the constructor's resolve property is untainted, the resolve function is set to undefined. Since undefined can't be a valid value for the resolve function, we can switch on it (in CallResolve) to directly call the PromiseResolve builtin. If the resolve property is tainted, we do an observable property lookup, save this value, and call this property later (in CallResolve). I ran this CL against the test262 tests locally and they all pass: https://github.com/tc39/test262/pull/2131 Spec: - https://github.com/tc39/ecma262/pull/1506 - https://github.com/tc39/proposal-promise-allSettled/pull/40 Bug: v8:9152 Change-Id: Icb36a90b5a244a67a729611c7b3315d2c29de6e9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1574705 Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org> Reviewed-by:Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#60957}
-
Michael Achenbach authored
TBR=tmrts@chromium.org Bug: v8:9145,v8:9098 Change-Id: Ib2170819f6d9aa00174fefb6bef4b0a27c11acfc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1578503Reviewed-by:
Sergiy Belozorov <sergiyb@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#60956}
-
andrew-cc-chen authored
Change-Id: I2bc21a353c871652daeac87eae62e1e6ae740b49 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1529638Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Junliang Yan <jyan@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#60955}
-
Michael Lippautz authored
This reverts commit 1ebf5f72. Reason for revert: Breaks TSAN Original change's description: > [api,heap] Remove deprecated Persistent APIs > > Removes APIs: > - MarkIndependent > - IsIndependent > - MarkActive > - RegisterExternalReference > > All weak persistent handles are now treated as independent. Users of > traced handles should already use v8::EmbedderHeapTracer. > > Bug: chromium:923361 > Change-Id: Ic90a647fe2ce9db92197ad6560e4907290805592 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1578459 > Commit-Queue: Michael Lippautz <mlippautz@chromium.org> > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > Cr-Commit-Position: refs/heads/master@{#60953} TBR=ulan@chromium.org,mlippautz@chromium.org Change-Id: I8281daf30b67c1b71ef6e65d8f13a59230ba0334 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:923361 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1578900Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#60954}
-
Michael Lippautz authored
Removes APIs: - MarkIndependent - IsIndependent - MarkActive - RegisterExternalReference All weak persistent handles are now treated as independent. Users of traced handles should already use v8::EmbedderHeapTracer. Bug: chromium:923361 Change-Id: Ic90a647fe2ce9db92197ad6560e4907290805592 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1578459 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#60953}
-
Shiyu Zhang authored
Change-Id: I9480650b23da4f5aa38a0634c1a7662bf88189d7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1551407Reviewed-by:
Georg Neis <neis@chromium.org> Reviewed-by:
Tobias Tebbi <tebbi@chromium.org> Commit-Queue: Shiyu Zhang <shiyu.zhang@intel.com> Cr-Commit-Position: refs/heads/master@{#60952}
-
Takuto Ikuta authored
As a preparation of trusty -> xenial migration, let me specify os dimension explicitly here. I added os dimension for the linux builders having tests property. I will change this dimension gradually with gradual swarming test bots trusty -> xenial migration. Currently this should not change ubuntu's version of bots running tests because v8 recipe module has default Ubuntu-14.04 dimension for linux. https://cs.chromium.org/chromium/build/scripts/slave/recipe_modules/v8/api.py?l=428&rcl=927948978a7a101fca66f07a784aeb3ddb6650c9 Bug: chromium:954890 Change-Id: Ib2404c5aaa54d6e8e47341394d6a757a9d99874a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1578659 Commit-Queue: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Sergiy Belozorov <sergiyb@chromium.org> Auto-Submit: Takuto Ikuta <tikuta@chromium.org> Reviewed-by:
-
Clemens Hammacher authored
The {Vector} class stores the size in a {size_t} since a while, but many accessors and constructors still accept an {int}. This CL removes all {int} uses except for the explicit {length()} accessor. It also adds a comment to avoid this accessor if possible. The {StrLength} function still has several users outside of vector.h, which I plan to remove in a follow-up CL. R=mstarzinger@chromium.org Bug: v8:8834 Change-Id: I33c5b0e8b8b2cb3531716c1d99e4516a13d6ba1f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1578480Reviewed-by: -
Clemens Hammacher authored
This CL fixes some issues with GC. 1) It removes dead code from the set of potentially dead code to avoid considering the same code for GC again and again. 2) It resets the {new_potentially_dead_code_size_} counter to avoid triggering too many GCs. 3) When code becomes dead after GC, do not unconditionally free it; just decrement its ref count (there might still be {WasmCodeRefScope}s holding the code alive). 4) Update the comment of the ref count to be more accurate. R=titzer@chromium.org Bug: v8:8217 Change-Id: I28e5a1fed74411b8473bb66ddbad3ffe7643f266 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1574518 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by:Ben Titzer <titzer@chromium.org> Cr-Commit-Position: refs/heads/master@{#60949}
-
Clemens Hammacher authored
This adds two counters for collecting the absolute size of freed code, and the percent of total generated code per module. R=titzer@chromium.org Bug: v8:8217 Change-Id: Ia065081104fbff6459791c919e0b18677ba45cc3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1573698 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by:
-
Sergiy Belozorov authored
This is dead code as no benchmarks seem to be using it and removing this additional logic will reduce maintenance cost for the perf infrastructure. R=machenbach@chromium.org, tmrts@chromium.org No-Try: true No-Tree-Checks: true Change-Id: I952af069d4d18d63624510b4c461fa1891703db9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1570008 Commit-Queue: Sergiy Belozorov <sergiyb@chromium.org> Reviewed-by:
-
Sergiy Belozorov authored
This is part of the refactoring to allow exporting more information about test execution to the recipes and upload this information to ChromePerf. This fixes running secondary even after primary run fails, which will allow us to differentiate between test and infra failures as latter ones will also affect refbuilds and re-runs without patch. R=machenbach@chromium.org, tmrts@chromium.org Bug: chromium:841700 Change-Id: I29ce49d2f8c5e73158f1d41a73c51f2b35929f36 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1570006 Commit-Queue: Sergiy Belozorov <sergiyb@chromium.org> Reviewed-by:
-
Clemens Hammacher authored
This is the next step to test the GC better: We zap the code region of {WasmCode} objects which are detected to be unused. This is tested in the future variant, so ClusterFuzz has a chance to catch missing references. R=titzer@chromium.org Bug: v8:8217 Change-Id: I75a63384a2a8e2ed68b9447e6ee4faa24037da93 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1571622Reviewed-by: -
Sergiy Belozorov authored
This is part of the refactoring to allow exporting more information about test execution to the recipes and upload this information to ChromePerf. R=machenbach@chromium.org,tmrts@chromium.org No-Try: true No-Tree-Checks: true Bug: chromium:841700 Change-Id: Iab400e8922231d8eac91a6fa22ce8f45053f7ac6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1569442Reviewed-by:
-
Michael Starzinger authored
The WebAssembly JavaScript Interface specifies[1] that exported functions are not constructors, hence do not have the "prototype" property. This is not true for asm.js exported functions which are expected to look like normal functions (or constructors). [1] https://webassembly.github.io/spec/js-api/index.html#exported-function-exotic-objects R=clemensh@chromium.org TEST=mjsunit/regress/regress-crbug-935800 BUG=chromium:935800 Change-Id: Idecacfb7f5d4668540589af95fd59872334c21a3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1578499 Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by:
Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#60943}
-
Simon Zünd authored
This CL implements the first set of diagnostic notifications. When Torque compilation fails, the language server translates the Torque error into a diagnostics notification and pushes it to the client. Note that per specification, the server is responsible to manage the state of all published diagnostics. This means that the server is also responsible for clearing out previous notifications if they become stale. Bug: v8:8880 Change-Id: Ief46dc1d94d1e5b7fa3e0048df494bfc05974031 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1569434Reviewed-by:
Sigurd Schneider <sigurds@chromium.org> Commit-Queue: Simon Zünd <szuend@chromium.org> Cr-Commit-Position: refs/heads/master@{#60942}
-
Michael Achenbach authored
This prints the current v8-specific processes on linux whenever the test driver emits a heart beat (i.e. no output for 30 seconds). This is to investigate the cause of currently hanging tests on linux. Bug: v8:9145 Change-Id: I857bb6d1c5f0b0917c64cdc0aa6076c6633f9dd6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1578438 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by:
Tamer Tas <tmrts@chromium.org> Reviewed-by:
-
Clemens Hammacher authored
EmbeddedVector lives on the stack only, and should not be implicitly copied or assigned. This also removes remaining uses of the removed Vector::set_start method. R=sigurds@chromium.org Bug: v8:9142 Change-Id: I829e6ffad6b1a30baa6c874265e92d615dd0c981 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1578458Reviewed-by:
-
Georg Neis authored
Before: 0x352ac49c2eb4 f4 4d898df0f10600 REX.W movq [r13+0x6f1f0] (WAAT??? What are we accessing here???),r9 After: 0x352ac49c2eb4 f4 4d898df0f10600 REX.W movq [r13+0x6f1f0],r9 Change-Id: I5f9af797de3c84117fd123204d9094251d18d07b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1571618Reviewed-by:
Jaroslav Sevcik <jarin@chromium.org> Commit-Queue: Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#60939}
-
Michael Achenbach authored
NOTRY=true TBR=sigurds@chromium.org Bug: v8:8963 Change-Id: Idf19be92f7f039a14838c87695666d5f6963e6a1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1575585Reviewed-by:
-
Matheus Marchini authored
R=bmeurer@chromium.org, jgruber@chromium.org, yangguo@chromium.org Bug: v8:9122 Change-Id: I6336d2fc0249269a749d99dcae7c172b2ccaac75 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1570582Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/b5c9a27..7dae72d Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/d8ce959..fb33e51 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/8dfc0bc..6d9913a TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: I94dc1ff83c0c6bbbe46ee83065895810b19f6dc8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1578278Reviewed-by:
-
- 21 Apr, 2019 1 commit
-
-
v8-ci-autoroll-builder authored
Rolling v8/test/wasm-js/data: https://chromium.googlesource.com/external/github.com/WebAssembly/spec/+log/f20b8e9..c46d4fa [spec] Work around Sphinx/Latex issue (#1004) (Andreas Rossberg) https://chromium.googlesource.com/external/github.com/WebAssembly/spec/+/c46d4fa TBR=ahaas@chromium.org,clemensh@chromium.org Change-Id: Id928f05d1ccec2f24d8bbe6eaca6bc646c58f6fc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1576818Reviewed-by:
-
- 20 Apr, 2019 1 commit
-
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/c0da152..b5c9a27 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/9f474a8..d8ce959 TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: Ifaea2c06ec5dd338d0ab6d9775a6cce30647d40d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1575828Reviewed-by:
-
- 19 Apr, 2019 5 commits
-
-
v8-ci-autoroll-builder authored
Rolling v8/test/wasm-js/data: https://chromium.googlesource.com/external/github.com/WebAssembly/spec/+log/d14d538..f20b8e9 [spec] Pre/post-conditions and some renamings in embedding interface (#1003) (Andreas Rossberg) https://chromium.googlesource.com/external/github.com/WebAssembly/spec/+/f20b8e9 TBR=ahaas@chromium.org,clemensh@chromium.org Change-Id: I08aa77e87d5c66b6cfde86d439c2dad4bf9b5aba Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1574374Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/cc63a88..c0da152 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/4e967e7..9f474a8 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/1e2cb15..8dfc0bc TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: I5e5ee21a818c6496cd8a3220ffa52d84b1e6c9f9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1574710Reviewed-by:
-
tzik authored
MicrotaskQueue associated to Context may be null after DetachGlobal, and triggering FinalizationGroup clean up on the detached context causes a crash. This CL fixes the crash by cancelling the clean up on such a context. Bug: chromium:937784 Change-Id: I57883ae0caf6c6bb35e482e441b6e09e921d9def Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1552500Reviewed-by:
Sathya Gunasekaran <gsathya@chromium.org> Reviewed-by:
-
Frank Tang authored
Design Doc: https://goo.gl/PGUQ1d Use template to share code between formatRange and formatRangeToParts Lazy crate DateIntervalFormat inside formatRange/formatRangeToParts to reduce performance impact. Bug: v8:7729 Change-Id: I130748a5ff7ca11235e6608195d365e58d440580 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1556573 Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by:
-
Frank Tang authored
Bug: v8:8699 Change-Id: I4e1f82132c3e48c21295ea7b0f3bcd24d5bd3c54 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1575019Reviewed-by:
-
- 18 Apr, 2019 7 commits
-
-
Frank Tang authored
Bug: v8:8604 Change-Id: Ieab15e55ed392019cc94de80d8e9c1a33f4d599a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1573038Reviewed-by:
-
Z Duong Nguyen-Huu authored
Per suggestion, we put this behind runtime flag in the mean time. Refactor some codes. Bug: v8:6831 Change-Id: Ibeb2a62b2a132971f8bc51c045bf0d2594eec198 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1566238 Commit-Queue: Z Nguyen-Huu <duongn@microsoft.com> Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#60927}
-
Frank Tang authored
Bug: v8:8702 Change-Id: I0d483be11fbb19b6555900f3f953eae531d3e8cb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1574618Reviewed-by:
-
George Burgess IV authored
We had one use of OS_CHROMEOS in mksnapshot. OS_CHROMEOS is defined if gn's `is_chromeos` is true, which checks `current_os`. `current_os != target_os` can happen if we're building with a non-default toolchain, which happens often on CrOS, since `mksnapshot` is a host binary. Tested by manually verifying that .text.hot.embedded now shows up on arm32/aarch64 builds of embedded.S. Bug: v8:9103 Change-Id: I038b56f4c18c7dd9a651ce676a977697dad14ae6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1573041 Commit-Queue: George Burgess <gbiv@chromium.org> Reviewed-by:
-
Santiago Aboy Solanes authored
This CL adds the representation changes from/to CompressedPointer to the other data types (excluding Tagged, which was done in a previous CL). Also adding missing write barriers for compressed values (WriteBarrierKindFor). Cq-Include-Trybots: luci.v8.try:v8_linux64_pointer_compression_rel_ng Cq-Include-Trybots: luci.v8.try:v8_linux64_arm64_pointer_compression_rel_ng Bug: v8:8977, v8:7703 Change-Id: Ieb4e6dd72371e858ba1da551f765e42581a51f90 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1571616Reviewed-by:
-
Maya Lekova authored
Bug: chromium:951400 Change-Id: Ib5454541e7c661649ccdb9771298ff90b3e9db5d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1571614 Commit-Queue: Maya Lekova <mslekova@chromium.org> Auto-Submit: Maya Lekova <mslekova@chromium.org> Reviewed-by:
-
Clemens Hammacher authored
There seems to be an issue where LTO inlines the icache flushing method but removes the save and restore of the r7 register which is clobbered for the icache flush syscall. This CL tries to avoid the bug. It's purely speculative, as we cannot reproduce the exact bug locally. R=jkummerow@chromium.org Bug: chromium:952759 Change-Id: I634fc4de3e8c4d1cb649384542c381d925b07a42 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1571619Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#60922}
-
