- 30 Jun, 2020 16 commits
-
-
Dominik Inführ authored
OldGenerationAllocationCounter() needs to be invoked in safepoint, otherwise invocation races with background threads incrementing the counter. First landed in https://crrev.com/c/2235544 and relanded in https://crrev.com/c/2259854 because of regressions. This CL also invokes UpdateNewSpaceAllocationCounter() in the safepoint. Bug: v8:10315 Change-Id: I6104bed0aad848250feecfe51d6d849b184a8842 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2260560 Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#68614}
-
Jakob Kummerow authored
This patch does not include support for RTTs for i31ref yet. Bug: v8:7748 Change-Id: Ifbeb8e305c2d0a57e4d5d6be761d046e330e0da1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2273135 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/master@{#68613}
-
Nico Hartmann authored
Bug: v8:10658 Change-Id: Iccc20acea0b506e8acffca944d19b70af011ee3d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2276035 Auto-Submit: Nico Hartmann <nicohartmann@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#68612}
-
Camillo Bruni authored
- Support loading combined trace json files from telemetry - Add "Blink RCS" source to separate blink details - Add prompt for naming newly loaded files - Add Group.addsToTotal variable for easier unclassified tracking Drive-by-fix: use let instead of var Change-Id: I5e471d8d1462987d1da98c2229090215c1fc6179 No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2273857 Commit-Queue: Camillo Bruni <cbruni@chromium.org> Reviewed-by: Sathya Gunasekaran <gsathya@chromium.org> Cr-Commit-Position: refs/heads/master@{#68611}
-
Andreas Haas authored
R=clemensb@chromium.org Bug: v8:10108 Change-Id: Ibfcef171e1a34153ea925aa657e66e7720c416ce Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2274130 Commit-Queue: Andreas Haas <ahaas@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#68610}
-
Dominik Inführ authored
Emit live bytes and evacuation mode as text for evacuated pages. Also emit the number of evacuated pages. Change-Id: Iadf1ac60f4fd35774f879277efb0b83fac39dd63 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2273136Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Cr-Commit-Position: refs/heads/master@{#68609}
-
Michael Achenbach authored
Mostly gc-related flags didn't flush out any bugs yet, but often reduce test performance and lead to timeouts. No-Try: true Bug: chromium:1044942 Change-Id: I2a7b55f78bfa3d597de1a5674658829e0812d01a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2273861Reviewed-by: Maya Lekova <mslekova@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#68608}
-
Michael Achenbach authored
Previously we ran baseline (e.g. ignition) and one random secondary comparison configuration (e.g. turbofan) from the list of experiments. But Clusterfuzz imposes limitations on the total amount of fuzz tests. Therefore this change enables more throughput by always running the default configuration (ignition_turbofan like V8 is shipped) additionally to the baseline and the secondary configuration. This, hence, doubles the number of comparisons we run, with less than 50% additional runtime, since the slow baseline configuration is only run once. The experiments table is updated accordingly. Explicit entries running ignition_turbofan are removed (as it always runs now), instead some of the other configurations are increased in their relative percentage. We also get a few new configurations that didn't run before (e.g. forcing the slow path on x86). No-Try: true Bug: chromium:1100114 Change-Id: I69b2a41d78c06e556b309743a2aace1053c22f91 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2270307Reviewed-by: Liviu Rau <liviurau@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#68607}
-
Simon Que authored
This is a reland of 32b685fa There was an unrelated breakage. See https://crbug.com/v8/10655#c10 Original change's description: > infra: Set gcc builders not to use Goma > > NOTRY=true > NOTREECHECKS=true > > Bug: chromium:1100009 > Change-Id: I67deb383d41e6609d5c3215e02422c8b1c16f8f4 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2272738 > Commit-Queue: Michael Achenbach <machenbach@chromium.org> > Reviewed-by: Michael Achenbach <machenbach@chromium.org> > Cr-Commit-Position: refs/heads/master@{#68593} TBR=liviurau@chromium.org NOTREECHECKS=true Bug: chromium:1100009 Change-Id: If59371bbe474383156effc6dfc92d848c304a416 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2276031Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#68606}
-
zeynepCankara authored
Indicium is a new tool that integrates all our Map and IC processing tools into one tool. This CL does not attempt to cleanly integrate the Map Processor and IC explorer, but provides an in initial starting point for further integration work. Bug: v8:10644 Change-Id: I753c116fd409c8c07613bf15f22e14aa1e8c8a0e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2259935 Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org> Reviewed-by: Sathya Gunasekaran <gsathya@chromium.org> Reviewed-by: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#68605}
-
Camillo Bruni authored
Bug: chromium:1098842 Change-Id: Id29edfda99f49a167a03b5158396a07559c75907 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2270231Reviewed-by: Clemens Backes <clemensb@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#68604}
-
Clemens Backes authored
It seems that the mix of atomic and non-atomic updates to the same memory location is not working correctly. One fix is changing all memory updates to be atomic. Another fix is removing the non-atomic access that happens while the workers are already running (using atomic accesses). This CL implements the latter. R=ahaas@chromium.org Bug: v8:10647, v8:10650 Change-Id: I84b4f3f442b6be3c4ea6e51962a523f443f5e43b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2273133Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#68603}
-
Manos Koukoutos authored
Change-Id: I04902e3f91dae6083b3de7630fd91d49ad805a2a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2272565 Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#68602}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/d83f4a5..3a5fbeb Rolling v8/third_party/aemu-linux-x64: FN-ckx_oV2JTqPuW3iMG50qdN5FgGqm-4XP9AkoLwPUC..I_sHBnheTA3cmFAjzkyUAhsmhpWXu82YLidstkjgsvIC Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/8353ff9..de622ae Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/6e6c67d..d9391fd Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/2479626..6849229 TBR=machenbach@chromium.org,tmrts@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I9e7c14e44cf7dc89f4a410a498af0ee306d9f0f2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2274519Reviewed-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@{#68601}
-
Zhao Jiazhong authored
On mips platform, call operations may be followed by trampolines, which leading to wrong information of the call instr's location in safepoint. This CL fix it by adding a last_call_pc_ to record the location. Besides, this CL also fix a bind operation in CheckTrampolinePool, which may try to use trampoline before it's emission. Change-Id: Ic0cbdb93afffa60a7389ee8177c381087fcaf52e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2095645 Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Reviewed-by: Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#68600}
-
Zhi An Ng authored
This reverts commit fa9c6e17. Reason for revert: Didn't fix the build. Original change's description: > Revert "Add support for __declspec(nocf)." > > This reverts commit 0c58583b. > > Reason for revert: https://crbug.com/v8/10656 and failures in https://ci.chromium.org/p/v8/builders/ci/V8%20Win64%20-%20msvc/14135 > > Original change's description: > > Add support for __declspec(nocf). > > > > __declspec(nocf) syntax was added in https://reviews.llvm.org/D72167 > > and annotates that checks should not be added on indirect calls > > within that function. > > > > BUG=chromium:584575 > > > > Change-Id: Ib2e2d2a827186a9c1fd3de15356b2b04d6a69e49 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2270707 > > Reviewed-by: Clemens Backes <clemensb@chromium.org> > > Commit-Queue: Will Harris <wfh@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#68590} > > TBR=wfh@chromium.org,clemensb@chromium.org > > Change-Id: Icec64feb44715a65e905a93e0c47fb37d4f11a09 > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: chromium:584575 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2274736 > Reviewed-by: Zhi An Ng <zhin@chromium.org> > Commit-Queue: Zhi An Ng <zhin@chromium.org> > Cr-Commit-Position: refs/heads/master@{#68598} TBR=wfh@chromium.org,clemensb@chromium.org,zhin@chromium.org Bug: chromium:584575 Change-Id: I0e305374c8325d87e4b18963da4e90802f136187 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2274356 Commit-Queue: Zhi An Ng <zhin@chromium.org> Reviewed-by: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#68599}
-
- 29 Jun, 2020 24 commits
-
-
Zhi An Ng authored
This reverts commit 0c58583b. Reason for revert: https://crbug.com/v8/10656 and failures in https://ci.chromium.org/p/v8/builders/ci/V8%20Win64%20-%20msvc/14135 Original change's description: > Add support for __declspec(nocf). > > __declspec(nocf) syntax was added in https://reviews.llvm.org/D72167 > and annotates that checks should not be added on indirect calls > within that function. > > BUG=chromium:584575 > > Change-Id: Ib2e2d2a827186a9c1fd3de15356b2b04d6a69e49 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2270707 > Reviewed-by: Clemens Backes <clemensb@chromium.org> > Commit-Queue: Will Harris <wfh@chromium.org> > Cr-Commit-Position: refs/heads/master@{#68590} TBR=wfh@chromium.org,clemensb@chromium.org Change-Id: Icec64feb44715a65e905a93e0c47fb37d4f11a09 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:584575 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2274736Reviewed-by: Zhi An Ng <zhin@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#68598}
-
Milad Farazmand authored
Change-Id: Iaa0075ea16c289a369b354f2f44b3d1161f2faac Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2273581Reviewed-by: Junliang Yan <jyan@ca.ibm.com> Commit-Queue: Milad Farazmand <miladfar@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#68597}
-
Michael Achenbach authored
TBR=santa NOTREECHECKS=true Change-Id: I629255ea3f65134bec8a1c7428b36426960aa311 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2274120 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#68596}
-
Zhi An Ng authored
This reverts commit 32b685fa. Reason for revert: https://ci.chromium.org/p/v8/builders/ci/V8%20Linux%20-%20vtunejit/36094 Original change's description: > infra: Set gcc builders not to use Goma > > NOTRY=true > NOTREECHECKS=true > > Bug: chromium:1100009 > Change-Id: I67deb383d41e6609d5c3215e02422c8b1c16f8f4 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2272738 > Commit-Queue: Michael Achenbach <machenbach@chromium.org> > Reviewed-by: Michael Achenbach <machenbach@chromium.org> > Cr-Commit-Position: refs/heads/master@{#68593} TBR=sque@chromium.org,machenbach@chromium.org Change-Id: Ia43f1ed69859d8face0adeefc820a06bf2e04c82 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:1100009 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2274086Reviewed-by: Zhi An Ng <zhin@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#68595}
-
Ng Zhi An authored
When filling stack slots, the start offset can be too large to fit into the immediate of a str instruction (which is used to handle remainders after stp). For example, a function with 32 i64 params will require 256 bytes reserved for the params, so the offset starts at 256 + 16 (instance) = 272. This does not fit into a int9, so we hit an UNREACHABLE case when emitting str. The fix here checks that start can fit in an unscaled immediate, and if it doesn't fallback to the general case. We could use the Str from macro-asesmbler, but that uses another instruction, so we are not saving anything. A check for IsImmLSUnscaled(-start-12) is sufficient because 12 is the largest possible value for remainder. So if -start-12 fits, everything else will fit. Bug: v8:10645 Change-Id: I1c415499ada3a807d5f3889f091150bfefdf471d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2267369 Commit-Queue: Zhi An Ng <zhin@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#68594}
-
Simon Que authored
NOTRY=true NOTREECHECKS=true Bug: chromium:1100009 Change-Id: I67deb383d41e6609d5c3215e02422c8b1c16f8f4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2272738 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#68593}
-
Ng Zhi An authored
Prototype f64x2.trunc on ARM for both ARM v7 and ARM v8. ARM v8 has support for vrintz, and for ARM v7 we fallback to runtime. Since ARM v8 uses vrintz, which is the same instruction used for F64 trunc (scalar), wasm-compiler reuses the Float64RoundTruncate check. Bug: v8:10553 Change-Id: I074d5b4172809915d4b37c59bd3b0dcbf9a45e1d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2268357 Commit-Queue: Zhi An Ng <zhin@chromium.org> Reviewed-by: Deepti Gandluri <gdeepti@chromium.org> Cr-Commit-Position: refs/heads/master@{#68592}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/2dc7c7a..d83f4a5 Rolling v8/third_party/aemu-linux-x64: UoYLOT0X6577j70eB9nPqYQs9Z3Nh5lA4I-pRtTchO0C..FN-ckx_oV2JTqPuW3iMG50qdN5FgGqm-4XP9AkoLwPUC Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/95c1f42..8353ff9 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/35c6274..6e6c67d Rolling v8/third_party/zlib: https://chromium.googlesource.com/chromium/src/third_party/zlib/+log/02daed1..8603eee Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/42b285f..2479626 TBR=machenbach@chromium.org,tmrts@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I3bd5df9f3c05eee0f135b0ee49708024edddc812 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2269870 Commit-Queue: Zhi An Ng <zhin@chromium.org> Reviewed-by: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#68591}
-
Will Harris authored
__declspec(nocf) syntax was added in https://reviews.llvm.org/D72167 and annotates that checks should not be added on indirect calls within that function. BUG=chromium:584575 Change-Id: Ib2e2d2a827186a9c1fd3de15356b2b04d6a69e49 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2270707Reviewed-by: Clemens Backes <clemensb@chromium.org> Commit-Queue: Will Harris <wfh@chromium.org> Cr-Commit-Position: refs/heads/master@{#68590}
-
Ng Zhi An authored
Prototype f64x2.floor on ARM for both ARM v7 and ARM v8. ARM v8 has support for vrintm, and for ARM v7 we fallback to runtime. Since ARM v8 uses vrintm, which is the same instruction used for Float64RoundDown (scalar), wasm-compiler reuses the Float64RoundDown check. Bug: v8:10553 Change-Id: I6f3d5c378a811ed94859535667aed1fa2d1ee552 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2265234Reviewed-by: Deepti Gandluri <gdeepti@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#68589}
-
Ng Zhi An authored
This modernizes python code without breaking Py2 compat. Ran with command: futurize --stage1 -w predictable_wrapper.py futurize --stage1 -w run-num-fuzzer.py futurize --stage1 -w run-tests.py futurize --stage1 -w v8_presubmit.py This only adds the absolute import, which use these semantics. It doesn't do anything differently in our case, these scripts are already doing absolute imports. But with these changes, running `futurize --stage2` will be less messy. Bug: v8:9871 Change-Id: I28182ab73dac6cfcbd544c2046026f14e5157eb3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2252555Reviewed-by: Tamer Tas <tmrts@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#68588}
-
Michael Lippautz authored
Bug: chromium:1056170 Change-Id: I24442979954f63dc8a2f8fd0494cc5d537b733a6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2273131 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Anton Bikineev <bikineev@chromium.org> Auto-Submit: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Anton Bikineev <bikineev@chromium.org> Cr-Commit-Position: refs/heads/master@{#68587}
-
Michael Achenbach authored
This shares the code of running the comparisons on the fuzz test and on the smoke tests. While this change retains behavior for running the fuzz test, the smoke test has slight changes in favor of code readability: 1. Smoke tests can now bail out on output suppressions (There are none now. And if we'd ever add any we'd need to write them in a way, such that they ignore the output of the smoke tests, which don't have much output anyways). 2. Crashes in smoke tests are now a hard failure. This is a desired feature anyways. It's unlikely that the smoke test crashes as then nothing would work. No-Try: true Bug: chromium:1100114 Change-Id: Ice3c6d18b549727c486a70756a72038c8b2029ac Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2273125 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Liviu Rau <liviurau@chromium.org> Cr-Commit-Position: refs/heads/master@{#68586}
-
Nico Hartmann authored
An 'arguments' array cannot be allocated in young space when its size exceeds kMaxRegularHeapObjectSize. In this case the optimizations in JSCreateLowering::ReduceJSCreateArguments are skipped. Bug: chromium:1098565 Change-Id: I30fdc78a1eb6e51fcd293785a46c9fd78995da9a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2273121Reviewed-by: Georg Neis <neis@chromium.org> Commit-Queue: Nico Hartmann <nicohartmann@chromium.org> Cr-Commit-Position: refs/heads/master@{#68585}
-
gengjiawen authored
Change-Id: I9ad6402561f06b4c2069c08f452e52a4d6b533eb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2270402Reviewed-by: Anton Bikineev <bikineev@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#68584}
-
Michael Achenbach authored
This adds a class representing all values needed for an execution. It simplifies the parameters passed to formatting functions and lifts the restriction of a first/second config pair in the options. This will allow to run more than two configs in a follow up. No-Try: true Bug: chromium:1100114 Change-Id: I568253b8ca3220870b8f5af615108140587680a8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2270550Reviewed-by: Tamer Tas <tmrts@chromium.org> Reviewed-by: Liviu Rau <liviurau@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#68583}
-
Clemens Backes authored
The test was taking more than a minute before CL https://crrev.com/c/2259933. Afterwards, it takes a lot longer, but I could never reproduce a hang locally. Let's re-enable and mark SLOW to increase the chance that it runs to completion. We can then see how much slower it really got. Also add some output that helps triaging in case it really hangs. R=ahaas@chromium.org Bug: v8:9506 Change-Id: I09a935ca0018517d45c6c008a099b8052bc45c47 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2273117 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#68582}
-
Jakob Kummerow authored
Relanding without changes, revert reason was fixed by: https://chromium-review.googlesource.com/c/v8/v8/+/2272564 Originally reviewed at: https://chromium-review.googlesource.com/c/v8/v8/+/2260566 Original description: RTTs are internally represented as Maps. To store supertype information, this patch introduces a WasmTypeInfo object, which is installed on Wasm objects' Maps and points at both the off-heap type information and the parent RTT. In this patch, rtt.sub always creates a fresh RTT. The canonicalization that the proposal requires will be implemented later. Bug: v8:7748 Change-Id: I7fd4986efa3153ac68037ec418ea617f3f7636e8 Tbr: ulan@chromium.org Tbr: tebbi@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2273123Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#68581}
-
Nico Hartmann authored
Bug: chromium:1100266 Change-Id: Iaa847a50e9a79261fe9d9050db5046fa99352eaa Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2273122 Auto-Submit: Nico Hartmann <nicohartmann@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#68580}
-
Michael Achenbach authored
This makes output and test-case suppressions independent of the used comparison configs and architecture. Such fine-grained suppressions were only needed during the inception of differential fuzzing, but by now, most remaining suppressions are implemented in d8 behind a flag. This prepares for running with more than two comparison configs in a follow up. No-Try: true Bug: chromium:1100114 Change-Id: I072769adb3ef7c6e6c43459aa23ac906f461b307 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2270095 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Liviu Rau <liviurau@chromium.org> Reviewed-by: Tamer Tas <tmrts@chromium.org> Cr-Commit-Position: refs/heads/master@{#68579}
-
Nico Hartmann authored
Bug: chromium:1100266 Change-Id: I20df6d0d5bdd07aa69c4eecf68c1d2152ddc1bec Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2272567Reviewed-by: Maya Lekova <mslekova@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#68578}
-
Michael Achenbach authored
It is obsolete to filter out error-message differences since the time we pass --correctness-fuzzer-suppressions to d8, which already stubs all messages: https://cs.chromium.org/chromium/src/v8/src/execution/messages.cc?l=1031 No-Try: true Bug: chromium:1100114 Change-Id: Iac42a8e2a32f9bae4034f79eaff429bf3ee41724 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2270024Reviewed-by: Maya Lekova <mslekova@chromium.org> Reviewed-by: Tamer Tas <tmrts@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#68577}
-
Michael Achenbach authored
This simplifies the lengthy main method by extracting some code and by replacing the scattered returns with exceptions. We introduce two exceptions for early bail-out. This enables helper methods on multiple layers. The early bail-out on time-out is moved to the point where it is detected. Previously on timeout and crash we also printed out the step number. Clusterfuzz doesn't parse this, it was only for statistical purposes, and the latest version of the experimental workbench only parses crashes and timeouts, not the step in which they happened. Hence, this CL removes those step numbers. Except the change described in the last paragraph, this CL doesn't intend to change behavior. No-Try: true Bug: chromium:1100114 Change-Id: Ie8c18f183e4fc538577f3eb49aaf6df1acd1e4e1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2270547Reviewed-by: Liviu Rau <liviurau@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#68576}
-
Camillo Bruni authored
This slows down promise benchmarks since we process all unhandled promises. Bug: vu:1099632 Change-Id: I2188a2842ec0a69ca93e5d406f10371ceff60f9b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2270235Reviewed-by: Michael Stanton <mvstanton@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#68575}
-