- 23 Mar, 2021 5 commits
-
-
Clemens Backes authored
This happens flakily on ClusterFuzz. It might not be relevant for users, but fixing it will allow ClusterFuzz to make more progress. R=szuend@chromium.org Bug: chromium:1190898 Change-Id: I7d0b705ff66e80e17ffc322b5d5fd5eb252d5965 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2778174Reviewed-by: Simon Zünd <szuend@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#73596}
-
Clemens Backes authored
The "DumpAsyncTaskStacksStateForTest" method just prints three counts, which is not helpful for the fuzzer and can create unwanted output during fuzzing. R=szuend@chromium.org Bug: chromium:1142437 Change-Id: I0192b3bf7d431ccf4938e6fc7a70f59ce43047a9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2778272Reviewed-by: Simon Zünd <szuend@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#73595}
-
Manos Koukoutos authored
LoadImmutable represents a load from a position in memory that is known to be immutable, e.g. an immutable IsolateRoot or an immutable field of a WasmInstanceObject. Because the returned value cannot change through the execution of a function, LoadImmutable is a pure operator and does not have effect or control edges. This will allow more aggressive optimizations of loads of fields of the Isolate and Instance that are known to be immutable. Requires that the memory in question has been initialized at function start even through inlining. Note: We may reconsider this approach once we have escape analysis for wasm, and replace it with immutable load/initialize operators that live inside the effect chain and are less restriced. Bug: v8:11510 Change-Id: I5e8e4f27d7008f39f01175ffa95a9c531ba63e66 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2775568Reviewed-by: Andreas Haas <ahaas@chromium.org> Reviewed-by: Georg Neis <neis@chromium.org> Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Cr-Commit-Position: refs/heads/master@{#73594}
-
Maya Lekova authored
This reverts commit bb2ca416. Reason for revert: WrapAround test is timing out on TSAN and closing the tree, please check https://ci.chromium.org/ui/p/v8/builders/ci/V8%20Linux64%20TSAN/36014/overview. Original change's description: > Reland [dict-proto] C++ implementation of SwissNameDictionary, pt. 10 > > This is a reland of > https://chromium-review.googlesource.com/c/v8/v8/+/2744138. It > shortens the runtime of the Copy and EnumerationOrder tests in > cctest/test-swiss-name-dictionary-csa for TSAN and CFI builds, as > compared to the original version. > > Original description: > > This CL is part of a series that adds the C++ implementation of > SwissNameDictionary, a deterministic property backing store based on > Swiss Tables. > > This CL adds the actual tests for SwissNameDictionary, defined in > test-swiss-name-dictionary-shared-tests.h, using the infrastructure > in test-swiss-name-dictionary-infra.[h|cc]. > > Bug: v8:11388 > Change-Id: Ia3f83f6e27be80bfdd63c2cb868638dc90d24cbc > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2778416 > Commit-Queue: Frank Emrich <emrich@google.com> > Reviewed-by: Igor Sheludko <ishell@chromium.org> > Cr-Commit-Position: refs/heads/master@{#73589} Bug: v8:11388 Change-Id: Ib95a7183cf9de35a33ec641bc1ec38915c3711c8 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2780294 Auto-Submit: Maya Lekova <mslekova@chromium.org> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#73593}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/5fcedaa..b43166a Rolling v8/third_party/aemu-linux-x64: bhg2KKy6t2GgDqorzVeY1StsCo2DnehaEbW3S_o1r7gC..osbsa1Jjgk8WbE3Ckv8288sgvejWZeAN8DB42wp0YV8C Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/999f35f..e46359d Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/e58ece5..392c407 Rolling v8/tools/luci-go: git_revision:92739fd8ab1f99ef55abfba4162eedb89fddfb7b..git_revision:edffd3478bb26469c614610d1a1c323b7e798b07 Rolling v8/tools/luci-go: git_revision:92739fd8ab1f99ef55abfba4162eedb89fddfb7b..git_revision:edffd3478bb26469c614610d1a1c323b7e798b07 Rolling v8/tools/luci-go: git_revision:92739fd8ab1f99ef55abfba4162eedb89fddfb7b..git_revision:edffd3478bb26469c614610d1a1c323b7e798b07 TBR=v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I1bf55969af87f822248be7858237f0b45961ff31 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2780675Reviewed-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@{#73592}
-
- 22 Mar, 2021 35 commits
-
-
Ng Zhi An authored
Fixed: v8:11591 Change-Id: I1d1d3ea94c969e17accb9651cd3e2dc29357ce12 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2780218Reviewed-by: Bill Budge <bbudge@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#73591}
-
Ng Zhi An authored
We splat two different values and then shuffle them together so that we can test pairwise addition of two different values. Bug: v8:11086 Change-Id: Id3bb34e9bfe21b6c5cb1d7eee3745c6c9e262f24 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2776513Reviewed-by: Deepti Gandluri <gdeepti@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#73590}
-
Frank Emrich authored
This is a reland of https://chromium-review.googlesource.com/c/v8/v8/+/2744138. It shortens the runtime of the Copy and EnumerationOrder tests in cctest/test-swiss-name-dictionary-csa for TSAN and CFI builds, as compared to the original version. Original description: This CL is part of a series that adds the C++ implementation of SwissNameDictionary, a deterministic property backing store based on Swiss Tables. This CL adds the actual tests for SwissNameDictionary, defined in test-swiss-name-dictionary-shared-tests.h, using the infrastructure in test-swiss-name-dictionary-infra.[h|cc]. Bug: v8:11388 Change-Id: Ia3f83f6e27be80bfdd63c2cb868638dc90d24cbc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2778416 Commit-Queue: Frank Emrich <emrich@google.com> Reviewed-by: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#73589}
-
Deepti Gandluri authored
Change-Id: I3ed8ff431fcfe93d61dd764a0d9f22fd20962f51 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2780219Reviewed-by: Zhi An Ng <zhin@chromium.org> Commit-Queue: Deepti Gandluri <gdeepti@chromium.org> Cr-Commit-Position: refs/heads/master@{#73588}
-
Ng Zhi An authored
Zero top lanes to ensure that we convert the low lanes of i32x4. Bug: v8:11265 Change-Id: Id53b65bada406c967c692b584210d4168e2c9183 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2776511Reviewed-by: Deepti Gandluri <gdeepti@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#73587}
-
Frank Tang authored
Make it ready to stage with harmony_intl_best_fit_matcher flag Bug: v8:11584 Change-Id: Ia6b9057b94dabe2a1edbea6855e2c42759ae1d5f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2773796 Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Shu-yu Guo <syg@chromium.org> Cr-Commit-Position: refs/heads/master@{#73586}
-
Andrew Comminos authored
Propagates CodeDeleteEvents to the CPU profiler based on finalizers registered in a WeakCodeRegistry, which tracks heap objects for weakly owned CodeEntries. Bug: v8:11054 Change-Id: I4c1f7885e982241724ca9f284f864da008ce9d75 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2751606Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Andrew Comminos <acomminos@fb.com> Cr-Commit-Position: refs/heads/master@{#73585}
-
Frank Emrich authored
This fixes a linking error introduced by CL https://chromium-review.googlesource.com/c/v8/v8/+/2757427 Tbr: solanes@chromium.org Change-Id: I8214218d29013d1a475a52044bc394d950211a6b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2780291Reviewed-by: Igor Sheludko <ishell@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Commit-Queue: Frank Emrich <emrich@google.com> Cr-Commit-Position: refs/heads/master@{#73584}
-
Ng Zhi An authored
When swizzle is called with a v128.const node, we can check that the indices are either all in bounds, or if they are out of bounds the top bit of each byte is set. This will match exactly pshufb behavior, and so we can omit the paddusb (and getting external reference). Bug: v8:10992 Change-Id: I5479a9eb92ebcfc12bedff5efd3e72bb4a43ff40 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2766222Reviewed-by: Deepti Gandluri <gdeepti@chromium.org> Reviewed-by: Georg Neis <neis@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#73583}
-
Ng Zhi An authored
Create a helper wasm-simd-utils to consolidate common helpers shared between simd and relaxed-simd. Drive-by cleanup to move RoundingAverageUnsigned out from overflowing-math (there is nothing overflowing about it). Bug: v8:11583 Change-Id: I9e24b4c1ee7f0bc00d0a3f85e7553991007a8d5a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2773784Reviewed-by: Clemens Backes <clemensb@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Deepti Gandluri <gdeepti@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#73582}
-
Junliang Yan authored
Change-Id: Icc3d98ee1f0ef2027b5ea0185f031ac84778b81b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2779034Reviewed-by: Milad Fa <mfarazma@redhat.com> Commit-Queue: Junliang Yan <junyan@redhat.com> Cr-Commit-Position: refs/heads/master@{#73581}
-
Frank Emrich authored
This CL adds a) swiss-hash-table-helpers.tq, which contains Torque counterparts for the C++ code in swiss-hash-table-helpers.h. b) various helpers required for that, including adding several CSA integer operations to base.tq. Bug: v8:11330 Change-Id: I6f6faf742334b5d107e84364ed793ad856d1cda1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2757427Reviewed-by: Santiago Aboy Solanes <solanes@chromium.org> Reviewed-by: Igor Sheludko <ishell@chromium.org> Commit-Queue: Frank Emrich <emrich@google.com> Cr-Commit-Position: refs/heads/master@{#73580}
-
Milad Fa authored
Change-Id: I88af87b611415753d1063d0b203f3c846fdecd57 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2778082Reviewed-by: Junliang Yan <junyan@redhat.com> Commit-Queue: Milad Fa <mfarazma@redhat.com> Cr-Commit-Position: refs/heads/master@{#73579}
-
Deepti Gandluri authored
Removing prefetch operations as per the vote in the github issue: https://github.com/WebAssembly/simd/pull/352 Bug:v8:11168 Change-Id: Ia72684e68ce886f8f26a7d3b5bea601be416dfab Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2771758Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Maya Lekova <mslekova@chromium.org> Reviewed-by: Zhi An Ng <zhin@chromium.org> Commit-Queue: Deepti Gandluri <gdeepti@chromium.org> Cr-Commit-Position: refs/heads/master@{#73578}
-
Milad Fa authored
Change-Id: Ic2f49e2808460100c9125542edd0f01e97f83acd Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2778335Reviewed-by: Junliang Yan <junyan@redhat.com> Reviewed-by: Milad Fa <mfarazma@redhat.com> Commit-Queue: Milad Fa <mfarazma@redhat.com> Cr-Commit-Position: refs/heads/master@{#73577}
-
Deepti Gandluri authored
This reverts commit ef808d3b. Reason for revert: Failures on TSAN: https://ci.chromium.org/p/v8/builders/ci/V8%20Linux64%20TSAN%20-%20no-concurrent-marking/2981? Original change's description: > [torque] Protect against printing Type* pointers > > I've noticed a frequent mistake within Torque is to use Type* pointers > with ostream's operator<<, which causes it to print a hex pointer rather > than a descriptive string. This can cause confusing error messages for > users of the Torque compiler. This change is an idea to prevent future > incidences of that problem by adding a template overload that will cause > a compilation failure if anybody tries to use Type* in this way. It > found two incorrect uses of Type*, which I've corrected. > > Bug: v8:7793 > Change-Id: I85fafb333a89f8a3fed4346bdd154d70846a63d1 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2748936 > Reviewed-by: Clemens Backes <clemensb@chromium.org> > Reviewed-by: Nico Hartmann <nicohartmann@chromium.org> > Commit-Queue: Seth Brenith <seth.brenith@microsoft.com> > Cr-Commit-Position: refs/heads/master@{#73574} Bug: v8:7793 Change-Id: Ieee470aa3cd176b9e1ad21fe39b9939edcef5bd6 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2778722 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Reviewed-by: Seth Brenith <seth.brenith@microsoft.com> Commit-Queue: Deepti Gandluri <gdeepti@chromium.org> Cr-Commit-Position: refs/heads/master@{#73576}
-
Clemens Backes authored
This reverts commit 8e6047e5. Reason for revert: Tests time out on TSan: https://ci.chromium.org/ui/p/v8/builders/ci/V8%20Linux64%20TSAN/36003/overview Original change's description: > [dict-proto] C++ implementation of SwissNameDictionary, pt. 10 > > This CL is part of a series that adds the C++ implementation of > SwissNameDictionary, a deterministic property backing store based on > Swiss Tables. > > This CL adds the actual tests for SwissNameDictionary, defined in > test-swiss-name-dictionary-shared-tests.h, using the infrastructure > in test-swiss-name-dictionary-infra.[h|cc]. > > Bug: v8:11388 > Change-Id: I5d91cede4f74b85a4101c5f2de3deda01a72edb2 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2744138 > Reviewed-by: Igor Sheludko <ishell@chromium.org> > Reviewed-by: Marja Hölttä <marja@chromium.org> > Commit-Queue: Frank Emrich <emrich@google.com> > Cr-Commit-Position: refs/heads/master@{#73572} Bug: v8:11388 Change-Id: I5d11e9f847545fe2b9c561ca8441eecb204bcfa1 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2779032 Auto-Submit: Clemens Backes <clemensb@chromium.org> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#73575}
-
Seth Brenith authored
I've noticed a frequent mistake within Torque is to use Type* pointers with ostream's operator<<, which causes it to print a hex pointer rather than a descriptive string. This can cause confusing error messages for users of the Torque compiler. This change is an idea to prevent future incidences of that problem by adding a template overload that will cause a compilation failure if anybody tries to use Type* in this way. It found two incorrect uses of Type*, which I've corrected. Bug: v8:7793 Change-Id: I85fafb333a89f8a3fed4346bdd154d70846a63d1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2748936Reviewed-by: Clemens Backes <clemensb@chromium.org> Reviewed-by: Nico Hartmann <nicohartmann@chromium.org> Commit-Queue: Seth Brenith <seth.brenith@microsoft.com> Cr-Commit-Position: refs/heads/master@{#73574}
-
Michael Achenbach authored
No-Try: true Bug: chromium:1126457 Change-Id: Ie78d441dea6f86531230ac10fc1e7c7f6bfe254c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2773350 Auto-Submit: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Liviu Rau <liviurau@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#73573}
-
Frank Emrich authored
This CL is part of a series that adds the C++ implementation of SwissNameDictionary, a deterministic property backing store based on Swiss Tables. This CL adds the actual tests for SwissNameDictionary, defined in test-swiss-name-dictionary-shared-tests.h, using the infrastructure in test-swiss-name-dictionary-infra.[h|cc]. Bug: v8:11388 Change-Id: I5d91cede4f74b85a4101c5f2de3deda01a72edb2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2744138Reviewed-by: Igor Sheludko <ishell@chromium.org> Reviewed-by: Marja Hölttä <marja@chromium.org> Commit-Queue: Frank Emrich <emrich@google.com> Cr-Commit-Position: refs/heads/master@{#73572}
-
Mike Stanton authored
When looking at Code objects from the compiler, we inquire whether the object is on a read only page. In TSAN builds, it's necessary to reload the memory because TSAN can't detect the safety of the operation. Fixed: v8:11590 Change-Id: Iaedd6e3f9f22241d4ef778f53a0405eaac8f76b6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2778276Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Michael Stanton <mvstanton@chromium.org> Cr-Commit-Position: refs/heads/master@{#73571}
-
Santiago Aboy Solanes authored
The instance type is set before setting the map inside an Object. It is relaxed and not non-atomic to prevent a false positive TSAN failure (see https://chromium-review.googlesource.com/c/v8/v8/+/2682641). Bug: v8:7790 Change-Id: Iddd28ffb06b5a882e77c4bf88bf8580df792f198 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2773042Reviewed-by: Georg Neis <neis@chromium.org> Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org> Cr-Commit-Position: refs/heads/master@{#73570}
-
Marja Hölttä authored
Bug: v8:11525 Change-Id: I9afd7095764fdb4b15c8a3492078073624b42a11 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2763869Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Shu-yu Guo <syg@chromium.org> Commit-Queue: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/master@{#73569}
-
Milad Fa authored
This reverts commit 0655aa05. Reason for revert: intermittent failures on s390 native: d8 --test test/wasm-spec-tests/tests/proposals/js-types/select.js --random-seed=-2107020726 --nohard-abort --testing-d8-test-runner --stress-background-compile --stress-wasm-code-gc --experimental-wasm-type-reflection --wasm-staging Original change's description: > Reland "s390x: [liftoff] implement CallRuntimeStub" > > This is a reland of 88c1ae95 > > Original change's description: > > s390x: [liftoff] implement CallRuntimeStub > > > > Change-Id: I505ea67af31006f3f233eef390f234cfc0188d6c > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2774479 > > Reviewed-by: Milad Fa <mfarazma@redhat.com> > > Commit-Queue: Junliang Yan <junyan@redhat.com> > > Cr-Commit-Position: refs/heads/master@{#73525} > > Change-Id: Id5d0ece78533439870fdc6b000026fe04e576448 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2774561 > Reviewed-by: Milad Fa <mfarazma@redhat.com> > Commit-Queue: Junliang Yan <junyan@redhat.com> > Cr-Commit-Position: refs/heads/master@{#73549} Change-Id: If81175b752738bd76ab612ef43448fa775cf3083 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2778333Reviewed-by: Milad Fa <mfarazma@redhat.com> Reviewed-by: Junliang Yan <junyan@redhat.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Milad Fa <mfarazma@redhat.com> Cr-Commit-Position: refs/heads/master@{#73568}
-
Clemens Backes authored
Stepping code that is left on the stack will repeatedly call the WasmDebugBreak function. This has no observable effect, except for severe slowdown of execution. In the linked bug, we were executing at least another few million instructions in the same frame, so it appeared that it never finishes. This CL fixes that by replacing stepping code with non-stepping code if the WasmDebugBreak runtime function is called from stepping code but we are not stepping (any more). Adding a test for this is difficult, since this only has an effect on performance. R=thibaudm@chromium.org Bug: chromium:1153308 Change-Id: I02feb04a156dfe81ca76ce26f0af131c470ef7a3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2775575 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by: Thibaud Michaud <thibaudm@chromium.org> Cr-Commit-Position: refs/heads/master@{#73567}
-
Thibaud Michaud authored
Popping values from an empty stack is allowed in unreachable code, but the stack height cannot be negative and stays at 0 instead. R=clemensb@chromium.org Bug: chromium:1190291 Change-Id: I84df7ab81ba6f5a9056c8341d88a4c47121363ad Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2778273Reviewed-by: Clemens Backes <clemensb@chromium.org> Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> Cr-Commit-Position: refs/heads/master@{#73566}
-
Clemens Backes authored
Especially "kNoReturnCall" is confusing, because it can be read as "a call that does not return", which is not meant here. This CL renames the enum to "TailCall" with the boolean values "kTailCall" and "kNoTailCall". Uses of the enum can be simplified to boolean checks directly. R=thibaudm@chromium.org Change-Id: I7d9664203031ddd27f0bdcf318c637b4c00d9be8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2775705Reviewed-by: Thibaud Michaud <thibaudm@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#73565}
-
Milad Fa authored
Change-Id: Icd46c44519a7cf524eba8a9ee3affdfb8f589bde Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2775716Reviewed-by: Junliang Yan <junyan@redhat.com> Commit-Queue: Milad Fa <mfarazma@redhat.com> Cr-Commit-Position: refs/heads/master@{#73564}
-
Santiago Aboy Solanes authored
Related: https://chromium-review.googlesource.com/c/v8/v8/+/2682641 Bug: v8:7790, v8:11353 Change-Id: Iefbc154b8bc7659e98a0bf8090e2d0cfa78b7063 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2773348Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org> Cr-Commit-Position: refs/heads/master@{#73563}
-
Clemens Backes authored
The frame types to skip are only used in the constructor, hence pass them as an initializer_list instead of template arguments. R=thibaudm@chromium.org Bug: v8:11384 Change-Id: I3ee57076a94514e5755f6f6541ebd9222306a634 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2775574Reviewed-by: Thibaud Michaud <thibaudm@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#73562}
-
Kim-Anh Tran authored
This fixes a bug in which CompileTopLevel has a pending exception that is never taken care of. This CL adds a check for the output of CompileTopLevel and clears the pending exceptions if existent. Also-by: bmeurer@chromium.org Bug: chromium:1190290 Change-Id: Ieba537d5af78fc35475f9547c240c70850bea608 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2773346 Commit-Queue: Kim-Anh Tran <kimanh@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#73561}
-
Clemens Backes authored
Generic wasm wrappers are enabled by default now (since https://crrev.com/c/2562241), so we can remove the flag from the nooptimization variant. Instead, we should have a configuration which tests --no-wasm-generic-wrapper to find bugs in the compiled wrappers earlier. Also add an entry for contradictory flags, and reformat that list to respect the 80 columns limit. R=machenbach@chromium.org CC=ahaas@chromium.org Bug: v8:10982 Change-Id: I780aaedbbf7fe761c39a41af1ff2db58c7447a76 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2773057Reviewed-by: Andreas Haas <ahaas@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#73560}
-
Ross McIlroy authored
If liveedit patches a script there might be a mismatch between the bytecode on a stackframe and the bytecode on the JSFunction for that same frame. This allows the patched bytecode on the JSFunction to be flushed which breaks the invariant that all JSFunctions with live stack activations are compiled. To prevent this disable bytecode flushing when liveedit patches a script. BUG=v8:11445 Change-Id: I79e7403dfb6dfc317d4313f8cab5118b12c67ed9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2775577 Auto-Submit: Ross McIlroy <rmcilroy@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/master@{#73559}
-
Manos Koukoutos authored
Change-Id: Iad4e33df76ce95b7f5543496fe1d2d7239f33c30 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2775566 Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#73558}
-
Manos Koukoutos authored
This is a more canonical type name, and is in line with {kVoidCode}. Change-Id: Iaae9524b6fb6ecaafd63ce81cf30e3d01ca3e525 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2775565 Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Reviewed-by: Simon Zünd <szuend@chromium.org> Cr-Commit-Position: refs/heads/master@{#73557}
-