- 28 Jul, 2021 17 commits
-
-
Junliang Yan authored
Change-Id: Ib10b00443fe1d46ccb75bd93ec0c855919bb563d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3058295Reviewed-by:
Milad Fa <mfarazma@redhat.com> Commit-Queue: Junliang Yan <junyan@redhat.com> Cr-Commit-Position: refs/heads/master@{#75964}
-
Yang Guo authored
Previously we do not tier down from baseline to interpreter, which breaks per-bytecode side effect checks (to check whether e.g. we are mutating a temporary object, which is not considered a side effect). R=leszeks@chromium.org Bug: chromium:1233401 Change-Id: Ie08b5352aa4c124421b4c9abce18326938bbc822 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3056981Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#75963}
-
Benedikt Meurer authored
Previously we'd report all property edges with symbol names as <symbol>, which was not very useful, especially with private class fields now seeing more adoption. Fixed: chromium:1232467 Change-Id: I53cf0811c4b83d016b988b687c6decbddd3c2fdd Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3055309 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#75962}
-
Santiago Aboy Solanes authored
Bug: v8:11600 Change-Id: I38696d64da4e321d966933179800376b7fdedaca Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3056987 Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org> Commit-Queue: Maya Lekova <mslekova@chromium.org> Auto-Submit: Santiago Aboy Solanes <solanes@chromium.org> Reviewed-by:
Maya Lekova <mslekova@chromium.org> Cr-Commit-Position: refs/heads/master@{#75961}
-
Clemens Backes authored
Found these when compiling the arm64 simulator for MSan (Release) and ASan (Debug and Release). Depending on the exact configuration (and compiler), different functions will get inlined and different symbols need to be available at link time. 1) Since GetRecoveredTrapCount is used in a unittest, it needs to be exported. 2) The thread-local g_thread_in_wasm_code cannot be exported on Windows, hence it cannot (safely) be used in unit tests. Use the {GetThreadInWasmThreadLocalAddress} function instead, which will return the address of that thread-local variable. R=ahaas@chromium.org, mseaborn@chromium.org Bug: v8:11955 Change-Id: I118f60c1580a8362f8232541576a1c41da7042bd Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3049077Reviewed-by:Andreas Haas <ahaas@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#75960}
-
Mythri A authored
Use write barrier when storing code into JSFunction::Code field. Earlier, code from SharedFunctionInfo was always a builtin and hence it was safe to skip write barrier there. With Sparkplug we could also store baseline code and hence it isn't safe to skip write barrier. Change-Id: I6a68ac759d619cdbeec8d4a37e9493d46f7aa790 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3056982Reviewed-by:
-
Leszek Swirski authored
The OSR entry stack check is needed as a function entry stack check to make sure the call isn't overflowing, but emitting it as part of the loop peeling meant that it would be within any exception handler ranges that the loop is in. In particular, this meant that code like this: try { loop { OSR(); } } catch {} would logically insert the entry stack check inside the try, and thus stack overflows of the function call would be caught within the function, and the function could continue runnning in an overflown state. Bug: chromium:1232875, chromium:1034322 Change-Id: I846c6f520fd3a897da016132419ad48043859c33 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3056980 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Reviewed-by:Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#75958}
-
Jakob Gruber authored
Drive-by: Remove invalid DCHECK(!is_deprecated) since we cannot guarantee this in a concurrent setting. Drive-by: Instead, check for deprecation during dependency validation. Drive-by: Remove addtl. invalid or outdated DCHECKs. Bug: v8:7790 Change-Id: Ia77a82976b987fe1eaca6178dac6c7b75fbf98fb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3041666Reviewed-by:
Georg Neis <neis@chromium.org> Commit-Queue: Georg Neis <neis@chromium.org> Auto-Submit: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#75957}
-
Jakob Kummerow authored
Bug: v8:11515 Change-Id: Ieece676f2f4ae258db8b7e1783c796ff6c0fa6f4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3055293Reviewed-by:
-
Liu Yu authored
Port 593fbb69 Bug: v8:12017 Change-Id: I0776820d0ab51950028da347d9d7d08acfb30386 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3058652 Auto-Submit: Liu yu <liuyu@loongson.cn> Reviewed-by:
Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Cr-Commit-Position: refs/heads/master@{#75955}
-
Maya Lekova authored
Bug: v8:11905 Change-Id: I845914a1c9dca760fd160fc2ff15aacc3f323993 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3056976 Commit-Queue: Maya Lekova <mslekova@chromium.org> Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org> Auto-Submit: Maya Lekova <mslekova@chromium.org> Reviewed-by:
Santiago Aboy Solanes <solanes@chromium.org> Cr-Commit-Position: refs/heads/master@{#75954}
-
Clemens Backes authored
Fix ia32 for v8_enable_webassembly=false. This is not a configuration that we test on CQ or the waterfall, but it was working at some point so this CL makes it compile again. R=zhin@chromium.org Change-Id: I78dafe08199c89ec24613a62a3085e923a51b43e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3056450Reviewed-by:
Zhi An Ng <zhin@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#75953}
-
Santiago Aboy Solanes authored
This means that we are now background serializing RefSerializationKind::kBackgroundSerialized classes on all configs. Bug: v8:7790 Change-Id: Iaa54718303e07e37a95d3f54d0c4c173d4174967 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3056453Reviewed-by:
-
Jakob Gruber authored
.. instead of recalculating them at the risk of getting different answers. In a concurrent setting, repeated type/rep calculations are not guaranteed to return the same answer. Instead, calculate them once and pass them into dependency creation methods. Note with this CL we now get the type/rep off the holder map and not the field owner map. The results should be identical and behavior should not change (verified by CHECKs). Bug: v8:7790 Change-Id: I2b4c3bb8907082c69448ca743d3c8740cd8f71f3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3055306Reviewed-by:
-
Liu Yu authored
Port edc349db Bug: v8:11235 Change-Id: Ie3cfadf97afcea4048c20bc1a5646f4e3c2a82ae Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3058061Reviewed-by:
-
Jakob Gruber authored
ComputeMinObjectSlack is called concurrently from background threads (when --concurrent-inlining) and must therefore be thread-safe. This CL adds a compiler-specific thread-safe variant of ComputeMinObjectSlack in addition to the plain old non-thread-safe one. Thread-safety is achieved through locking: on the bg thread, a shared lock when traversing transitions, and on the main thread, an additional exclusive critical section when overwriting prototype transitions. Tbr: leszeks@chromium.org Bug: v8:7790,v8:12010,chromium:1231901 Change-Id: If5af83df1ab896b22477921449fb5ba4c8d3e8a3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3045342 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Auto-Submit: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/e3754f7..96a4da9 Rolling v8/buildtools/third_party/libc++abi/trunk: https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libcxxabi/+log/bfcda91..24e92c2 Rolling v8/buildtools/third_party/libunwind/trunk: https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libunwind/+log/23a5972..e6a0f63 TBR=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com Change-Id: I9042ee9ede0949807a83329e8045811adad06fe2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3058290Reviewed-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@{#75948}
-
- 27 Jul, 2021 16 commits
-
-
Milad Fa authored
This cl uses the newly added instructions on power10 for extracting the sign bits. Change-Id: I9e4fa3bdd7fa5fc7004695c1d3ac29e3906d5207 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3056506Reviewed-by:
Junliang Yan <junyan@redhat.com> Commit-Queue: Milad Fa <mfarazma@redhat.com> Cr-Commit-Position: refs/heads/master@{#75947}
-
Marja Hölttä authored
Bug: v8:11111 Change-Id: I09e918a3f8c50e10691c8ab4718b7c4ae9184000 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3055303 Commit-Queue: Marja Hölttä <marja@chromium.org> Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#75946}
-
Milad Fa authored
Port ec717160 Original Commit Message: This is no longer used, tail calls are dealt with inside of VisiTailCall. R=zhin@chromium.org, joransiu@ca.ibm.com, junyan@redhat.com, midawson@redhat.com BUG= LOG=N Change-Id: I44cac6f77ce79d47806b3f504c3bad1d88475a25 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3055307Reviewed-by:
-
Ng Zhi An authored
We can emit a 9-byte nop, so leave more padding, otherwise the disassembled code looks a bit off, e.g.: 0x265ef7799a73 5b3 e902010000 jmp 0x265ef7799b7a <+0x6ba> 0x265ef7799a78 5b8 0f1f840000000000 nop 0x265ef7799a80 5c0 83c004 addl rax,0x4 Bug: v8:11879 Change-Id: I697e97b45644e28e544705b972c88702f7f27ffc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3054255Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/ff4b382..e3754f7 Rolling v8/buildtools/linux64: git_revision:d565aa3e72dd9e81da9595ee8c9d7b24cb45c48b..git_revision:c0a2d23c21e87f27f5af3e5dc2a99f2ef3480b9e Rolling v8/buildtools/third_party/libc++abi/trunk: https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libcxxabi/+log/e8bf577..bfcda91 Rolling v8/buildtools/third_party/libunwind/trunk: https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libunwind/+log/d7b11d7..23a5972 Rolling v8/third_party/aemu-linux-x64: jIoBgZ-iUWXLCCH8YkbLabPLzKXZ54b27lb6trJpzpUC..LiTUyHa0AyC2fE72v094aZIjv1aTdQEZfYm-LIJVQIwC Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/9ac1fdf..10f6e4b Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/131233f..2a8bb1c Rolling v8/tools/luci-go: git_revision:9ee8b1d719c0d3c268e0e19282351ca78024af2d..git_revision:75ff299b9adf969190cafebe902255856a346f0b Rolling v8/tools/luci-go: git_revision:9ee8b1d719c0d3c268e0e19282351ca78024af2d..git_revision:75ff299b9adf969190cafebe902255856a346f0b Rolling v8/tools/luci-go: git_revision:9ee8b1d719c0d3c268e0e19282351ca78024af2d..git_revision:75ff299b9adf969190cafebe902255856a346f0b TBR=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com Change-Id: Ie13b5864c24cc43c5e49ba794af1ca0024fd8e01 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3056498Reviewed-by:
-
Milad Fa authored
Port 593fbb69 Original Commit Message: Currently we first construct the frame (via {TurboAssembler::EnterFrame}), then we spill the instance to the respective slot (via {LiftoffAssembler::SpillInstance}). Instead, we should already spill the instance as part of frame construction. That allows for a more compact instruction to be used ("push" instead of "mov" on Intel), and on arm64 even allows to merge pushing into an existing instruction (where we currently push the zero register x31 instead). This makes the prologue more similar to what TurboFan generates in {TurboAssembler::AssembleConstructFrame} (which does not use {TurboAssembler::EnterFrame}). R=clemensb@chromium.org, joransiu@ca.ibm.com, junyan@redhat.com, midawson@redhat.com BUG= LOG=N Change-Id: I0b87d73776b59ade36faea2f4772c63c89eb740e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3056455Reviewed-by:
-
Jakob Kummerow authored
It was previously only passed to compilation units in src/bigint/, but inconsistencies arise when it's not passed to other compilation units that #include src/bigint/bigint.h. Fixed: chromium:1233397 Change-Id: Idb310d8c13bad12766699086574aa2c3869eb56c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3056452Reviewed-by:
-
Vasili Skurydzin authored
This changes builtin definition so that builtins are now located in GL .text section, to maintain their alignment in the resulting binaries and make sure the off-heap code is aligned to kCodeAlignment. Change-Id: I4662ca59273fa2dd11e7ecf63969597b9dd9664b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3054431Reviewed-by:
-
Al Muthanna Athamina authored
Include changes from https://crrev.com/ff4b382aca5ad5077883bec9e4ac3dc64776902a Bug: chromium:1233409 Change-Id: I571feec6e3d56ade7ad167f2e0b7bebb5c9ddf8b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3055300 Commit-Queue: Almothana Athamneh <almuthanna@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Auto-Submit: Almothana Athamneh <almuthanna@chromium.org> Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#75939}
-
Clemens Backes authored
Currently we first construct the frame (via {TurboAssembler::EnterFrame}), then we spill the instance to the respective slot (via {LiftoffAssembler::SpillInstance}). Instead, we should already spill the instance as part of frame construction. That allows for a more compact instruction to be used ("push" instead of "mov" on Intel), and on arm64 even allows to merge pushing into an existing instruction (where we currently push the zero register x31 instead). This makes the prologue more similar to what TurboFan generates in {TurboAssembler::AssembleConstructFrame} (which does not use {TurboAssembler::EnterFrame}). R=ahaas@chromium.org Bug: v8:12017 Change-Id: Ibb4a38d2049cff66fec9450db4f7f375d006beac Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3055302Reviewed-by: -
Thibaud Michaud authored
R=jkummerow@chromium.org Bug: v8:11992 Change-Id: If62f2cdc080364dec796a836321110bf571769ef Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3049075 Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> Reviewed-by:
-
Santiago Aboy Solanes authored
Some of the fields come from MapRef calls and we have to still serialize them while Map is bg-serialized. An alternative would be to move them to MapData but that comes with a cost since different maps with the same descriptor array wouldn't share said data. Bug: v8:7790 Change-Id: I25d8eaf7b0a8bf7de0f21272cc6f86cc172b8b08 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3008640 Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org> Reviewed-by:
-
Michael Achenbach authored
This reverts commit 67960ba1. Reason for revert: This has been properly fixed by https://crrev.com/c/3053740. Now dcheck_always_on already defaults to false for subprojects like V8 and no other switch is required. The switch didn't fully work anyways due to https://crbug.com/1231890. Original change's description: > Reland "[build] Add V8-specific dcheck_always_on" > > This is a reland of cecc666f > > Depends on: > https://crrev.com/c/3043611 > > Original change's description: > > [build] Add V8-specific dcheck_always_on > > > > This makes the V8 dcheck control independent of Chromium's and > > prepares switching Chromium's default behavior without affecting V8 > > developers or builders. > > > > Preparation for: https://crrev.com/c/2893204 > > > > Bug: chromium:1225701 > > Change-Id: I520b96019b04196f4420716ff3500ebd6c21666f > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3038528 > > Reviewed-by: Leszek Swirski <leszeks@chromium.org> > > Commit-Queue: Michael Achenbach <machenbach@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#75827} > > Bug: chromium:1225701 > Change-Id: I56568b78592addba01793d2d14f768c9ee10103d > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3041670 > Reviewed-by: Liviu Rau <liviurau@chromium.org> > Commit-Queue: Michael Achenbach <machenbach@chromium.org> > Cr-Commit-Position: refs/heads/master@{#75839} Bug: chromium:1225701, chromium:1231890 Change-Id: I7e27f5774d8e162977f30f685da4b15dadcc1084 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3055294Reviewed-by:
Liviu Rau <liviurau@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#75935}
-
Jakob Gruber authored
The implementation came in with https://chromium-review.googlesource.com/758999. This feature was never enabled by default, is not used anywhere, and is not on any standardization path. Bug: v8:10953 Change-Id: Ia2b0a556c1fb504a4cd05bdfa9f0a9c5be608d26 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3053589Reviewed-by:
Mathias Bynens <mathias@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#75934}
-
Santiago Aboy Solanes authored
Bug: v8:7790 Change-Id: I0d875d4a350d4e101534d82129cd7ef90f342738 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3008639Reviewed-by:
-
Georg Neis authored
Bug: chromium:1228036 Change-Id: I5abe7009920d2c8f81f024c9ae7bb6b13607da1a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3054119 Commit-Queue: Georg Neis <neis@chromium.org> Reviewed-by:
Hannes Payer <hpayer@chromium.org> Cr-Commit-Position: refs/heads/master@{#75932}
-
- 26 Jul, 2021 7 commits
-
-
Ng Zhi An authored
This is no longer used, tail calls are dealt with inside of VisiTailCall. Bug: v8:11879 Change-Id: I3e5b74c61c959a6697bc3fd05c8f9aa60cce9fa7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3049570Reviewed-by:
-
Junliang Yan authored
Change-Id: I99448ed94e8ef0cb2ea9fdf6e629757bda595d54 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3054472Reviewed-by:
-
Peter Kasting authored
Bug: chromium:1203071 Change-Id: I09724552731594ddf18358d29cdc243cb696652d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3053617Reviewed-by:
-
Zhi An Ng authored
This reverts commit 14941067. Reason for revert: https://ci.chromium.org/ui/p/v8/builders/ci/V8%20Linux%20-%20gc%20stress/34588/overview Original change's description: > Reland^2 "[sparkplug] Enable sparkplug by default on desktop" > > This is a reland of 0f79565b > which is a reland of 85e6c4b6 > GC-stress issue was still flushing, now fixed for real with > https://crrev.com/c/3054117. > > Relanding without changes. > > TBR=verwaest@chromium.org > > Original change's description: > > Reland "[sparkplug] Enable sparkplug by default on desktop" > > > > This is a reland of 85e6c4b6 > > GC-stress issue was flushing, fixed with https://crrev.com/c/3048172. > > Relanding without changes. > > > > TBR=verwaest@chromium.org > > > > Original change's description: > > > [sparkplug] Enable sparkplug by default on desktop > > > > > > Bug: v8:11420 > > > Change-Id: I07ac7f30b5ffffe40170ac15d5df0d3bf8a53523 > > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3041418 > > > Auto-Submit: Leszek Swirski <leszeks@chromium.org> > > > Commit-Queue: Leszek Swirski <leszeks@chromium.org> > > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > > Cr-Commit-Position: refs/heads/master@{#75868} > > > > Bug: v8:11420 > > Change-Id: I44ac0e4a5df07db79fa50db3134cdae3af41c88c > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3053588 > > Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> > > Commit-Queue: Leszek Swirski <leszeks@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#75916} > > Bug: v8:11420 > Change-Id: I24c7aea81ca58c339fc3bcc904663bdefb93106b > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3054118 > Reviewed-by: Leszek Swirski <leszeks@chromium.org> > Commit-Queue: Leszek Swirski <leszeks@chromium.org> > Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> > Cr-Commit-Position: refs/heads/master@{#75926} Bug: v8:11420 Change-Id: Id7ad213f9bf463d9d167c8420c85038043d9523c No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3054436 Auto-Submit: Zhi An Ng <zhin@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@{#75928}
-
Jakob Kummerow authored
Bug: v8:11515 Change-Id: I1353726c9e81c3601258202fe56c05ffd16a4a25 Fixed: chromium:1232733 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3054112Reviewed-by:
Marja Hölttä <marja@chromium.org> Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#75927}
-
Leszek Swirski authored
This is a reland of 0f79565b which is a reland of 85e6c4b6 GC-stress issue was still flushing, now fixed for real with https://crrev.com/c/3054117. Relanding without changes. TBR=verwaest@chromium.org Original change's description: > Reland "[sparkplug] Enable sparkplug by default on desktop" > > This is a reland of 85e6c4b6 > GC-stress issue was flushing, fixed with https://crrev.com/c/3048172. > Relanding without changes. > > TBR=verwaest@chromium.org > > Original change's description: > > [sparkplug] Enable sparkplug by default on desktop > > > > Bug: v8:11420 > > Change-Id: I07ac7f30b5ffffe40170ac15d5df0d3bf8a53523 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3041418 > > Auto-Submit: Leszek Swirski <leszeks@chromium.org> > > Commit-Queue: Leszek Swirski <leszeks@chromium.org> > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#75868} > > Bug: v8:11420 > Change-Id: I44ac0e4a5df07db79fa50db3134cdae3af41c88c > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3053588 > Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> > Commit-Queue: Leszek Swirski <leszeks@chromium.org> > Cr-Commit-Position: refs/heads/master@{#75916} Bug: v8:11420 Change-Id: I24c7aea81ca58c339fc3bcc904663bdefb93106b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3054118Reviewed-by:
-
Clemens Backes authored
Handle large frames by doing an explicit check to see if there is enough remaining stack space before the stack limit. The bailout which can be removed then is being triggered on more than 1 percent of all functions, so this is expected to improve compile time by several percent, because we avoid the costly TurboFan compilation for those >1%. The code follows the same pattern as on arm, see https://crrev.com/c/3046180. R=ahaas@chromium.org Bug: v8:11235 Change-Id: I0d359ae5fe0126da7ade860f596cfc108e7fd1d0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3054114Reviewed-by:
-
