- 09 Sep, 2019 4 commits
-
-
Dominik Inführ authored
Slots are always valid inside an invalidated area when outside the respective object's current size. This allows us to remove the size from the InvalidatedSlots data structure. This change was enabled by https://crrev.com/c/1771793. Reland after revert in https://crrev.com/c/1783106, this CL was not the culprit of the issue (chromium:1000404). Bug: v8:9454 Change-Id: I823d34670515924bf74200daa21a834044087310 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1787431Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Reviewed-by: Sigurd Schneider <sigurds@chromium.org> Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Cr-Commit-Position: refs/heads/master@{#63607}
-
Dominik Inführ authored
Filtering was reverted in https://crrev.com/c/1773252 because of chromium:998256, but this issue seems to be unrelated. Bug: v8:9454 Change-Id: Ie266976c8fc664fe2a7395198a010307f5297f25 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1792163Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Cr-Commit-Position: refs/heads/master@{#63606}
-
Tom Tan authored
It is not recommended to define type alias in C++ header file. cctest defines type alias `using Label=CodeAssemblerLabel` in anonymous namespace under namespace `v8::internal::compiler` in test-code-assembler.cc. This is fine because this type alias is expected to take effect only in this .cc file. But in jumbo build, multiple source files are combined as a single one, and the previous `Label` type alias could shadow definition of `Label` from other header file (for example, v8/src/codegen/label.h which is included by another .cc file) This is totally unexpected and triggers bad class layout and accessing in the latter .cc file for the places where `Label` is referenced. This change fixes cctest from Windows ARM64 jumbo build, but it applies to other architectures too. Bug: chromium:893460 Change-Id: Ib2e9df76f6e3371b3940649668c5d13e6b36f028 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1788537Reviewed-by: Jakob Gruber <jgruber@chromium.org> Commit-Queue: Tom Tan <Tom.Tan@microsoft.com> Cr-Commit-Position: refs/heads/master@{#63605}
-
Simon Zünd authored
ScopeIterator was changed to re-parse the whole script instead of just a single function. The CL in question went through a few iterations. At one point, it was necessary to wrangle the source position of generator functions to correctly identify their closure scope. This is no longer necessary and this CL removes the manual source position adjustment. Change-Id: If1a61ed32a903997b70a62cd464198f3dffa385a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1792162 Auto-Submit: Simon Zünd <szuend@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#63604}
-
- 08 Sep, 2019 1 commit
-
-
v8-ci-autoroll-builder authored
Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/4ebfe46..efce0d1 TBR=machenbach@chromium.org,tmrts@chromium.org Change-Id: I20fe4d684b2ee9a7c80fdc062147dc2489922c65 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1789616Reviewed-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@{#63603}
-
- 07 Sep, 2019 2 commits
-
-
Ross McIlroy authored
Currently this is very similar to TurboFan's OptimizeGraph phase, but avoids a number of passes to reduce optimization time. With time this will have more differences. BUG=v8:9684 Change-Id: Id416385e55fa52e1103fd103032c6db86c17f047 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1784295 Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Reviewed-by: Maya Lekova <mslekova@chromium.org> Cr-Commit-Position: refs/heads/master@{#63602}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/031af13..6ff11c8 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/52c5d30..fcd6915 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/208e343..4ebfe46 Rolling v8/third_party/googletest/src: https://chromium.googlesource.com/external/github.com/google/googletest/+log/565f1b8..3f05f65 Rolling v8/third_party/instrumented_libraries: https://chromium.googlesource.com/chromium/src/third_party/instrumented_libraries/+log/b1c3ca2..e289777 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/56e3b98..51c4acf TBR=machenbach@chromium.org,tmrts@chromium.org Change-Id: I8ff99937a6e5aa70ebbc57c2dac0579dd417e7ad Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1789604Reviewed-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@{#63601}
-
- 06 Sep, 2019 15 commits
-
-
Thibaud Michaud authored
GetMaxBackgroundTasks should return 0 in predictable mode, since compilation is done in the foreground. R=clemensh@chromium.org Change-Id: I4a617cadb53ca91ee21e40c46a93d54e2a1ceb8b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1789301 Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#63600}
-
Swapnil Gaikwad authored
This is a reland of 8b89a7c3 Reland after disabling the test getting deadlocked with '--gc_stress' flag. The CL was reverted because of the 'wasm/grow-shared-memory' test from the mjsunit test suite deadlocked for the 'gc_stress' variant. This is the known issue (v8:9221) and the deadlocking test is now disabled ( https://chromium.googlesource.com/v8/v8.git/+/1c8981e3f4729b7a8220a8823e0a0d45f2a4b788). Original change's description: > Update GetIterator bytecode to load and call object[Symbol.iterator] > > The functionality of the GetIterator bytecode introduced previously is > now extended from loading the @@iterator property to calling the property > as well. This change basically absorbs the functionality of additional > two bytecodes - Star, CallProperty0 in the GetIterator bytecode. > Importantly, this change handles the cases of eager and lazy deoptimization > in the middle of the bytecode, i.e., lazy deopt for LdaNamedProperty and > eager deopt of the CallProperty0 bytecode, using the continuation builtins. > This mechanism can work as a template for the future bytecode that require > handling such inter-bytecode deopt scenario. The tests evaluating the eager > and lazy deopt scenarios are also included. > > Bug: v8:9489 > Change-Id: I93eb022bbc3d37582407820aa8482a343cac6c12 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1758313 > Commit-Queue: Swapnil Gaikwad <swapnilgaikwad@google.com> > Reviewed-by: Leszek Swirski <leszeks@chromium.org> > Reviewed-by: Georg Neis <neis@chromium.org> > Reviewed-by: Tobias Tebbi <tebbi@chromium.org> > Cr-Commit-Position: refs/heads/master@{#63528} Bug: v8:9489,v8:9221 Change-Id: I4286255aef457bfdbbe5eb50fc6dabdf9c0955b1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1787427Reviewed-by: Tobias Tebbi <tebbi@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Swapnil Gaikwad <swapnilgaikwad@google.com> Cr-Commit-Position: refs/heads/master@{#63599}
-
Peter Marshall authored
This is a reland of 096d9c56 Fixed DEPS files which were not caught by presubmit trybot Original change's description: > [tracing] Roll perfetto @ 28b633cd > > This catches up with [1] that make the proto include path > relative to the project root rather than ./protos/ > > [1] https://android-review.googlesource.com/c/platform/external/perfetto/+/1108421 > > Cq-Include-Trybots: luci.v8.try:v8_linux64_perfetto_dbg_ng > Bug: v8:8339 > Change-Id: I1f2dec93120142ea61cee864e4bf76a6947d958d > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1776088 > Reviewed-by: Peter Marshall <petermarshall@chromium.org> > Reviewed-by: Tamer Tas <tmrts@chromium.org> > Commit-Queue: Primiano Tucci <primiano@chromium.org> > Auto-Submit: Primiano Tucci <primiano@chromium.org> > Cr-Commit-Position: refs/heads/master@{#63584} Bug: v8:8339 Change-Id: I70e8b2d4520c620d02d5251d14bd61b90fb1d73f Cq-Include-Trybots: luci.v8.try:v8_linux64_perfetto_dbg_ng Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1789143 Commit-Queue: Peter Marshall <petermarshall@chromium.org> Reviewed-by: Tamer Tas <tmrts@chromium.org> Cr-Commit-Position: refs/heads/master@{#63598}
-
Swapnil Gaikwad authored
Disable the 'wasm/grow-shared-memory' test from the mjsunit test suite for all the 'gc_stress' variants. The test is currently disabled only for executions with the combination of 'gc_stress' and 'slow_path'. With the --gc-stress flag enabled, the test time outs as a result of deadlock or fails with the DCHECK error because of the known issue. Bug: v8:9221 Change-Id: Ia2cbbb6f1e5678e5583176fcdd557bd8760234e2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1789290Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Swapnil Gaikwad <swapnilgaikwad@google.com> Cr-Commit-Position: refs/heads/master@{#63597}
-
Clemens Hammacher authored
Since C++14, we can use a switch in a constexpr function. R=ahaas@chromium.org Bug: v8:9686, v8:9687 Change-Id: I082a7be6c54d6c705b678f19aa56bdb7a3313f80 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1786284Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#63596}
-
Clemens Hammacher authored
Since we do not support gcc < 5 any more, we can switch to C++14 now. Gcmole is the only tool preventing this currently. R=mstarzinger@chromium.org Bug: v8:9687, v8:9690 Change-Id: Ie7fee25061bdf6f1e7f156bc150b7142c824f5d1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1787426Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#63595}
-
Clemens Hammacher authored
This reverts commit b1c3ca2a. Reason for revert: TSan issues: https://ci.chromium.org/p/v8/builders/ci/V8%20Linux64%20TSAN/28147 Original change's description: > [heap] Reschedule concurrent marking tasks earlier > > Currently we reschedule concurrent marking tasks if all tasks finish. > This is too conservative and we can improve performance by rescheduling > finished tasks without waiting for all other tasks. > > As a drive-by this also changes task_count_ to total_task_count_. > > Change-Id: If0b3bd45ce6d52f6bcd0065dd8d3efe9ea84184a > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1789142 > Commit-Queue: Ulan Degenbaev <ulan@chromium.org> > Reviewed-by: Omer Katz <omerkatz@chromium.org> > Cr-Commit-Position: refs/heads/master@{#63593} TBR=ulan@chromium.org,omerkatz@chromium.org Change-Id: I5e6b406a021c8fd4834e346e02388552ee3e0036 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1789287Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#63594}
-
Ulan Degenbaev authored
Currently we reschedule concurrent marking tasks if all tasks finish. This is too conservative and we can improve performance by rescheduling finished tasks without waiting for all other tasks. As a drive-by this also changes task_count_ to total_task_count_. Change-Id: If0b3bd45ce6d52f6bcd0065dd8d3efe9ea84184a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1789142 Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by: Omer Katz <omerkatz@chromium.org> Cr-Commit-Position: refs/heads/master@{#63593}
-
Simon Zünd authored
This CL changes the {ScopeIterator} to re-parse the whole script instead of just the immediate function. The result are accurate parent scopes, which will enable better variable lookup for debug evaluation. Drive-by: Remove unused IGNORE_NESTED_SCOPES ScopeIterator::Option and refactor ScopeIteartor::Next. Change-Id: I6cb9d303fe5f84da4f4b11c6e2057f07c232316c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1771785Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Simon Zünd <szuend@chromium.org> Commit-Queue: Simon Zünd <szuend@chromium.org> Cr-Commit-Position: refs/heads/master@{#63592}
-
Clemens Hammacher authored
This reduces the size per runtime stub slot by using the same sequence we plan to use for far jumps. Note that alignment is not an issue here, since runtime stub slots are never patched. R=mstarzinger@chromium.org CC=joey.gouly@arm.com Bug: v8:9477 Change-Id: I38666c8fce93a977bc5b9ca5fafc54f6ae739f12 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1784293 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#63591}
-
Maya Lekova authored
Bug: v8:7790 Change-Id: Id213800587f08df544bea4f9fca7460d136baeb5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1786280 Commit-Queue: Maya Lekova <mslekova@chromium.org> Reviewed-by: Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#63590}
-
Maya Lekova authored
Bug: v8:7790 Change-Id: I798555bb6fbbee2ce2a3dc4bb22a84ff881792f0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1784294Reviewed-by: Georg Neis <neis@chromium.org> Commit-Queue: Maya Lekova <mslekova@chromium.org> Cr-Commit-Position: refs/heads/master@{#63589}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/e030d8a..031af13 Rolling v8/third_party/android_ndk: https://chromium.googlesource.com/android_ndk/+log/6258275..89e8db0 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/06605b0..52c5d30 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/624bf6e..208e343 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/2fef805..56e3b98 TBR=machenbach@chromium.org,tmrts@chromium.org Change-Id: I58a44985730b1c1c2865e5552303c8b835b43390 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1786034Reviewed-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@{#63588}
-
Zhang, Shiyu authored
Shadowing key is used to exclude non-enumerable keys when iterating over the prototype chain. This CL skips adding shadowing key for end prototype to improve for-in performance. It can improve the performance of below microbench by ~50%. Object.prototype.foo = function() {}; let obj = { a:0, b:1 }; let start = Date.now(); for (let i = 0; i<1e6; i++) { for (var j in obj) {} } console.log(Date.now() - start); This CL also improves the score of JetStream2-tagcloud-SP case by 8% on IA Chromebook. Contributed by tao.pan@intel.com Change-Id: I456082c08bf70f1f450ff54f657cdab26eb7bc2b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1781113Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Shiyu Zhang <shiyu.zhang@intel.com> Cr-Commit-Position: refs/heads/master@{#63587}
-
Shu-yu Guo authored
Expressions in class heritage position do not have access to the inheriting class's private names, only its lexical bindings. The parser currently uses the same scope chain for both. This CL makes scopes in class heritage position skip their outer class when resolving private names. Whether a scope needs to skip is kept as a bit on various scope-related data structures. See implementation doc at https://docs.google.com/document/d/1d3o_SQqcICxfjLMw53OOaiIQux0ppNHQJnjZHtCQLwA Bug: v8:9177 Change-Id: I77e491a9d4a261131274f12ddf052af7ac31a921 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1769486 Commit-Queue: Shu-yu Guo <syg@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Mathias Bynens <mathias@chromium.org> Cr-Commit-Position: refs/heads/master@{#63586}
-
- 05 Sep, 2019 18 commits
-
-
Santiago Aboy Solanes authored
This reverts commit 096d9c56. Reason for revert: Broke presubmit https://ci.chromium.org/p/v8/builders/ci/V8%20Presubmit/6371 Original change's description: > [tracing] Roll perfetto @ 28b633cd > > This catches up with [1] that make the proto include path > relative to the project root rather than ./protos/ > > [1] https://android-review.googlesource.com/c/platform/external/perfetto/+/1108421 > > Cq-Include-Trybots: luci.v8.try:v8_linux64_perfetto_dbg_ng > Bug: v8:8339 > Change-Id: I1f2dec93120142ea61cee864e4bf76a6947d958d > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1776088 > Reviewed-by: Peter Marshall <petermarshall@chromium.org> > Reviewed-by: Tamer Tas <tmrts@chromium.org> > Commit-Queue: Primiano Tucci <primiano@chromium.org> > Auto-Submit: Primiano Tucci <primiano@chromium.org> > Cr-Commit-Position: refs/heads/master@{#63584} TBR=primiano@chromium.org,petermarshall@chromium.org,tmrts@chromium.org Change-Id: I3ff6afa58869399b2a352cd489acdd2894ef138c No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:8339 Cq-Include-Trybots: luci.v8.try:v8_linux64_perfetto_dbg_ng Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1787433Reviewed-by: Santiago Aboy Solanes <solanes@chromium.org> Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org> Cr-Commit-Position: refs/heads/master@{#63585}
-
Primiano Tucci authored
This catches up with [1] that make the proto include path relative to the project root rather than ./protos/ [1] https://android-review.googlesource.com/c/platform/external/perfetto/+/1108421 Cq-Include-Trybots: luci.v8.try:v8_linux64_perfetto_dbg_ng Bug: v8:8339 Change-Id: I1f2dec93120142ea61cee864e4bf76a6947d958d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1776088Reviewed-by: Peter Marshall <petermarshall@chromium.org> Reviewed-by: Tamer Tas <tmrts@chromium.org> Commit-Queue: Primiano Tucci <primiano@chromium.org> Auto-Submit: Primiano Tucci <primiano@chromium.org> Cr-Commit-Position: refs/heads/master@{#63584}
-
Clemens Hammacher authored
{JavaScriptFrame::GetParameters} allocates a new {FixedArray}, hence all object references need to be handified to survive that allocation. R=mstarzinger@chromium.org Bug: chromium:1000635 Change-Id: I76df5ac109bdb6999fe897bdafaf2175344ecca4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1787429Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#63583}
-
Leszek Swirski authored
This is a reland of 981aafaf It adds double checks to LoadFieldByIndex in the optimizing compiler, which are likely the source of the crashes. Original change's description: > Reland "[ic] In-place Double -> Tagged transitions" > > This is a reland of 0736599a. > This is a reland of 7e1fbe8f. > > Original change description: > > [ic] In-place Double -> Tagged transitions > > > > With no more MutableHeapNumber, we can make Double -> Tagged transitions > > in-place, at the cost of an extra map check when accessing double fields > > to make sure they are still doubles. > > > > Bug: v8:9606 > > Change-Id: I74ff39ed6fba62ee223cd37dfe761f7d73020e1c > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1743973 > > Reviewed-by: Tobias Tebbi <tebbi@chromium.org> > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > Commit-Queue: Leszek Swirski <leszeks@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#63374} > > TBR=verwaest@chromium.org, tebbi@chromium.org > > Bug: v8:9606 > Change-Id: I2d1b7416064d743582f4983fb868316b7e8a4cf2 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1777661 > Reviewed-by: Leszek Swirski <leszeks@chromium.org> > Commit-Queue: Leszek Swirski <leszeks@chromium.org> > Cr-Commit-Position: refs/heads/master@{#63499} TBR=verwaest@chromium.org Bug: v8:9606 Bug: chromium:997989 Change-Id: Iccfff8e5c6306c9ee4f6c62767dce883b1c6f743 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1784288Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Tobias Tebbi <tebbi@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/master@{#63582}
-
Joshua Litt authored
Implements match indices for regexp, as specified by https://github.com/tc39/proposal-regexp-match-indices, a stage 3 TC39 proposal. This implementation is hidden behind the '--harmony-regexp-match-indices' flag. Regexp match indices extends the JSRegExpResult object with an array of indices of matches, as well as a dictionary of capture names to match indices. Bug: v8:9548 Change-Id: Ia9efcee00d997dda6158539b8d0f4c4e5965e5e7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1771379 Commit-Queue: Joshua Litt <joshualitt@chromium.org> Reviewed-by: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#63581}
-
Santiago Aboy Solanes authored
Bug: v8:6949 Change-Id: I8f0de9e202f41c78e24c4d73c54b198a52122dac Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1784296 Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org> Reviewed-by: Mythri Alle <mythria@chromium.org> Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#63580}
-
Dan Elphick authored
Since const variables are immutable, ignore SetMaybeAssigned for them. Bug: chromium:999450, chromium:1000170, v8:8510 Change-Id: Idc1b71677b3d03bb63cc025017c119710b8f392d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1782170 Commit-Queue: Dan Elphick <delphick@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/master@{#63579}
-
Santiago Aboy Solanes authored
TNodified: * Jump (both versions) * JumpBackward * JumpIfTaggedEqual * JumpIfTaggedNotEqual * JumpConditional * LoadOsrNestingLevel Removed slopiness from Advance's parameter. Renamed "delta" to jump_offset for JumpXXX arguments. They were called jump_offset in .h and delta in .cc. Bug: v8:6949 Change-Id: I6b34391dcb2ee881670d04edac9382258f6bcb51 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1782821 Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org> Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#63578}
-
Santiago Aboy Solanes authored
TNodified: * code-assembler * TailCallBytecodeDispatch * interpreter-assembler * GetContextAtDepth * ExportParametersAndRegisterFile * ImportRegisterFile * Dispatch * DispatchToBytecode * DispatchToBytecodeHandlerEntry * DispatchWide * return type of Jump (Jumps are coming in another CL) * LoadBytecode Removed DispatchToBytecodeHandler since it was unused. Removed target_bytecode parameter of DispatchToBytecodeHandlerEntry since it was unused. Bug: v8:6949 Change-Id: Icd3ded28cc1fd1dc528219dd83cf646e67c9b878 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1782838 Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org> Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> Reviewed-by: Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/master@{#63577}
-
Santiago Aboy Solanes authored
TNodified from interpreter-generator: * SwitchOnSmiNoFeedback * CreateFunctionContext * CreateEvalContext * SwitchOnGeneratorState since they were using some of the interpreter-assembler now TNodified methods. Bug: v8:6949 Change-Id: I0055100428232e8bdc79cb4356954bac52f4a30d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1781689 Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org> Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#63576}
-
Andreas Haas authored
There was no problem with the original CL. I just had a problem with my local git branches. Original message: The implementation on wasm-bigint has been done, as far as I can tell. There are no spec tests yet, only an out-dated copy of the original spec tests which don't pass anymore. Therefore I disabled all the tests for now and created a tracking bug at https://crbug.com/v8/9673. TBR=adamk@chromium.org Bug: v8:7741, v8:9673 Change-Id: Ida7ccda4547cf3fdcdff151d8b02946b7aa534ca Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1787420Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#63575}
-
Michael Hablich authored
TBR=machenbach@chromium.org NOTRY=true Change-Id: I2873acd03b9673dedf587d21e35101ad163fd580 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1787425 Commit-Queue: Michael Hablich <hablich@chromium.org> Reviewed-by: Michael Hablich <hablich@chromium.org> Cr-Commit-Position: refs/heads/master@{#63574}
-
Santiago Aboy Solanes authored
TNodify related methods: * BytecodeArrayTaggedPointer * DispatchTablePointer (renamed from DispatchTableRawPointer) * GetAccumulatorUnchecked SloppyTNodify SetAccumulator's argument. Marking some tests as slow, due to TNodification. Bug: v8:6949 Change-Id: I3a56c47247828ec1313ce69ce76064efedf57776 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1782162Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> Reviewed-by: Tobias Tebbi <tebbi@chromium.org> Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org> Cr-Commit-Position: refs/heads/master@{#63573}
-
Clemens Hammacher authored
Node now requires gcc >=6.3, and we do not test on gcc <5.4 any more. Thus remove a special case for gcc <5. R=machenbach@chromium.org Bug: v8:9686 Change-Id: Ifffddec611c15b704aa292a65e87cd770d85ea7b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1786283Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#63572}
-
Michael Achenbach authored
Bug: v8:9687 Change-Id: Ia9e82e1565d2dca595f5a231281d415f423b3421 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1787421Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#63571}
-
Tobias Tebbi authored
This is a safe to merge hot-fix to tackle https://crbug.com/983764. To be reverted after merging to M77. Bug: chromium:983764 Change-Id: I3cd27481f224b352ef6bcf9dde21a8f77616acff Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1786285Reviewed-by: Maya Lekova <mslekova@chromium.org> Commit-Queue: Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/master@{#63570}
-
Clemens Hammacher authored
Node now requires gcc >=6.3, and we do not test on gcc <5.4 any more. Thus remove a hack for gcc <5. R=machenbach@chromium.org Bug: v8:9686 Change-Id: I503c6b76d40499bbe45fb83996e0dfebf86f3395 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1786281Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#63569}
-
Michael Starzinger authored
This makes sure no underlying ArrayBuffer is reserved for modules that don't declare a module. For the case where a memory is declared but the initial size is 0, we still reserve a buffer in case of trap handlers. R=ahaas@chromium.org BUG=v8:9678 Change-Id: I837b8f257b63eb4111646806b899074babd7c9f7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1784290Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#63568}
-